![]() If you’d like, your table can also include other optional fields with information about the interviews. “Scheduled” (To mark events that are ready to be synced to Google Calendar, when you’re ready) ![]() “Tentative” or “Not yet scheduled” (To designate interviews that aren’t yet ready to be pushed to Google Calendar) This status field should include at least these two options: Call this field “Status,” or something similar. Call these fields “Start Time” and “End Time,” or something similar.Ī single select field that will contain select options designating the status of each interview. Two date fields, one of which will contain the start date and time of the event, and the other one which will contain the end date and time of the event. In this table, you’ll need the following: In your Airtable base, you should have a table (called “Interviews,” or something similar) that lists the specific interviews that you’re trying to schedule. In this example, we’ll use a simple applicant tracking system (shown below) that a recruiting team is using to schedule interview sessions.Ĭlick the Copy base button in the embedded base below to add this example automation to one of your workspaces. You’ll also need to have an Airtable base in which you’re organizing the events that you’d like to schedule. First, you’ll need an Airtable account and a Google Calendar account. To build this automation, you’ll need a couple of ingredients. Preparing a base to automatically schedule calendar events Owners/Creators - Create, delete, duplicate, configure, or rename an automation and edit an automation's description.Įditors - View an automation's configuration or copy an automation's URL. You can use similar techniques to add a Google Calendar automation in other bases, and you can also make a copy of the base below, which already has the automation built into it for you. In this article, we’ll show you step-by-step instructions for how to add this automation to an existing Airtable base for an applicant tracking system. There are also many Make experts hanging out there who can answer other Make questions.Learn how to create an automation that will automatically schedule Google Calendar events. However, the one downside to Make is that there can be a bit of a learning curve with Make, which is why I created this basic navigation video for Make, along with providing the link to Make’s free training courses. Make has much better tech support than Zapier. Make is SIGNIFICANTLY cheaper than Zapier, even though it is way more powerful than Zapier.Ĥ. For example, Make has an entire library of hundreds of functions & tools built into the platform that let you manipulate your data in ways that Zapier doesn't allow at all - including groups of Airtable records at once, which Zapier also doesn't allow.ģ. Make is SIGNIFICANTLY more powerful than Zapier. Also, Make has a purely visual drag-and-drop environment that makes it much easier to visualize entire automations.Ģ. Just as one example out of dozens of examples, Zapier only allows 3 conditional branches, whereas Make allows unlimited conditional branches. Make has none of the limitations that Zapier has. ![]() The main problems that I have with Zapier are best described by discussing the main advantages that Make has over Zapier:ġ. I would always recommend using Make over Zapier. Mentioned Zapier, but I would not recommend using Zapier. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |