Let's Calendar Zapier integrationAutomate Let's Calendar with Zapier.
Let's Calendar Zapier integration: 1 trigger, 1 action, 0 searches. Zapier can add people to a Let's Calendar campaign when they sign up somewhere else, and read your campaign list. Works on the free plan. Below: costs, connection, a first Zap, what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Let's Calendar Zapier integration does for you
The Let's Calendar Zapier integration connects your Let's Calendar account to Zapier so that registrations reach your campaigns without anyone typing them in. Let's Calendar is built to send calendar invites in bulk for events and webinars, and to hold a slot in each recipient's calendar. Zapier brings the people in from the apps where they first show up.
The work happens mostly in one action, Add Registration to Campaign, and three results come up again and again. Form to campaign: someone fills in your signup form and lands in the right campaign, no export, no copy-paste. Spreadsheet to campaign: a colleague adds a row to a shared sheet and that person is registered too, which suits lists built by hand. CRM to campaign: a new contact in your CRM gets registered to the campaign you picked once in the Zap (set once, then used for every new contact).
What Zapier does not do here matters just as much. There is no search, so a Zap cannot check whether someone is already registered before adding them. The only trigger, Get Campaign List, reads your list of campaigns; it does not report new registrations or event changes. And the action needs a campaign that already exists: Zapier does not create one for you. If you are weighing other tools for this, see n8n vs Zapier and our Zapier review.
Zapier vocabulary in one minute
Eight words come back all over this page. Here is what each one means in plain terms.
- Zap
- The automation you build in Zapier: one trigger first, then one or more actions that run every time that trigger event happens.
- Trigger
- The event that starts a Zap. Once the Zap is on, Zapier waits for it, here or in any other app you start from.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, such as a new registration.
- Task
- The unit Zapier bills. One action that completes successfully counts as one task, and your plan allowance is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer that depends on your plan. An instant trigger is reported by its app the moment it happens.
- Filter
- A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it right there otherwise.
- Connection
- Your Let's Calendar account, linked to Zapier one time and then reused by every Zap step that needs Let's Calendar.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
What a Let's Calendar Zap really costs
Triggers never cost a task, and neither does Zapier checking for new items. The bill comes from Add Registration to Campaign: each registration that goes through counts as one task.
- Cost per registration1 task
- Free plan100 tasks a month
- Free plan Zap size2 steps
- Premium appNo
A registration that fails is not counted. A Zap that registers someone and then sends a message spends two tasks per person. The free plan gives you 100 tasks a month and Zaps of two steps: a trigger plus one action. Add a filter or a second action and you need a paid plan. Let's Calendar is not a premium app, so it runs on the free plan. Get Campaign List is a polling trigger, so how often Zapier checks it follows the grid below.
Connect Let's Calendar to Zapier in three steps
- 01
Open the Apps page
Sign in to Zapier and go to the Apps page of your account. Before you start, check that you have a Let's Calendar account of your own, plus access to any campaign you do not own but want a Zap to fill.
- 02
Add Let's Calendar
Click + Add connection, type Let's Calendar in the search box of the dialog and pick it from the list. Then click Add connection: a new browser tab opens on the Let's Calendar side.
- 03
Sign in and grant access
In that tab, sign in to Let's Calendar and grant Zapier access to the account. The connection now sits on your Apps page, and every Zap step that uses Let's Calendar reuses it without asking again.
Your first Zap: keep a sheet of your Let's Calendar campaigns
GoalEach campaign that Get Campaign List hands over and that passes your condition becomes a new row in your spreadsheet; the trigger test shows what it actually carries.
- 01
Create the Zap and pick the trigger
In Zapier, start a new Zap, choose Let's Calendar as the app that starts it and Get Campaign List as the event. Select the Let's Calendar connection you added earlier.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you see exactly what this trigger returns and map the next steps on a real campaign.
- 03
Add the filter
Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule and the value. Pick a rule that matches the field type, or nothing ever gets through.
- 04
Add the spreadsheet action
Add the action in your spreadsheet app and map what the trigger brought back into the columns. With a filter, this Zap is multi-step and needs a paid plan.
- 05
Test, then publish
Run each step once and read what comes back. When the row lands where you expect it, click Publish. Zapier then checks the campaign list at your plan's interval.
The Let's Calendar trigger
1 event starts a Zap when something happens in Let's Calendar. Zapier checks for them at the interval your plan allows.
Get Campaign List
Polling triggerIn Zapier“Triggers when user fetch Let's Calendar Campaign list.”
Starts the Zap when your list of Let's Calendar campaigns is fetched, and passes that list to the next steps. Zapier's own description is one line and says nothing about new campaigns, so test it once to see what it brings back before you build on it.
The Let's Calendar action
Let's Calendar gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Add Registration to Campaign
ActionIn Zapier“This will add a new registration record to your Let's Calendar Campaign”
Adds a new registration record to the Let's Calendar campaign you select, built from the email address the earlier steps carried in.
When a Let's Calendar Zap breaks
Zapier attaches no help article to Let's Calendar, and no rate limit is documented for it. The risks are the general ones every Zap runs into.
None of them shows up as a big red error at first. They show up as people missing from a campaign, a task count that drops faster than planned, or a Zap that looks on but does nothing. When one of them hits, start with Zapier troubleshooting.
Earlier signups never come through
A Zap only reacts to what happens after it is switched on. Signups from before you published are never registered; moving that backlog into the campaign is a separate job.A loop that eats your tasks
A Zap that writes into the very place its own trigger watches sets itself off again and again, and burns through the task count fast. Keep the two apart.A bulk import gets held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back instead of registering everyone.The same campaign does not fire twice
On a polling trigger such as Get Campaign List, Zapier keeps track of what it has already seen, so an item it already handled does not start the Zap again.
Need help automating Let's Calendar with Zapier?
A person reads every message.
