AddCal Zapier integrationAutomate AddCal with Zapier.
The AddCal Zapier integration gives you 2 triggers, 4 actions and 0 searches. Both triggers are instant, AddCal is not a premium app, and every operation is about RSVPs, events and calendar invites. Here is what each one does and what it costs.
Verified Trustpilot reviews · AI, automation & growth agency
What the AddCal Zapier integration actually does
AddCal builds "Add to Calendar" links that work across the big calendar platforms, and it can collect RSVPs or send real calendar invites. Plugging it into Zapier means two things: an RSVP or an invite reply in AddCal can start work in your other tools, and your other tools can create events, RSVPs and invites in AddCal without anyone copying data by hand.
Three results people usually build. A live guest list for a workshop. A trainer running paid workshops points New RSVP at a spreadsheet, so each sign-up becomes a row the moment it arrives. A heads-up when someone bails. A sales team hosting a product demo uses Invite Responded to post a message in the team chat when a prospect declines, so someone can follow up the same day. Events created from your planning tool. An ops manager who keeps the quarter's webinars in a project board sends each new item to Create Event, with title, start date and end date mapped from the card.
What Zapier does not do here: there is no search step for AddCal, so a Zap cannot look up an existing event or RSVP by itself. Events you pick in Create RSVP or Send Calendar Invite come from a list filled by the account, and only events with the right feature switched on appear in it. Nothing that happened before the Zap was switched on is picked up either.
There is no n8n or Make page for AddCal on this site yet. If you are still choosing a platform, the Make vs Zapier comparison sets out the criteria side by side, and the Zapier training covers the basics if this is your first Zap.
Zapier vocabulary in one minute
Eight words come back on every line of this page. Each one in plain English, once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for that event to happen.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills. One task is one action that completes successfully; your plan's count is a count of those.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a scheduled check.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only unseen ones.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
- Connection
- Your AddCal account linked to Zapier once, then reused by every step in every Zap that touches AddCal.
What an AddCal Zap really costs
Short version: the two AddCal triggers are free to run, and you pay in tasks for each action that goes through.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps
- Trigger typeBoth triggers instant
A trigger never costs a task, and neither does Zapier looking for new data. Each action that succeeds counts once, so a Zap with three actions uses three times as much as a Zap with one. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a second action, or a filter, and you have a multi-step Zap (anything beyond one trigger and one action), which needs a paid plan. On the interval grid, polling triggers wait 15 minutes on Free; AddCal's triggers are both instant, so that grid never applies to them.
Connect AddCal to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an AddCal account first, plus access to any event you do not own yourself but want the Zap to touch.
- 02
Pick AddCal
Type AddCal in the search box of the dialog, select it from the results, then click Add connection. A new browser tab opens on the AddCal side, ready for the sign-in.
- 03
Sign in and grant access
Log in to AddCal in that tab and allow Zapier to reach the account. The connection is then saved, and every AddCal step of every Zap you build later reuses it.
Your first Zap: log every invite reply
GoalA conference organizer wants each accept, maybe or decline on a speaker invite written to a tracking sheet, then announced in the team channel.
- 01
Create the Zap
Start a new Zap, choose AddCal as the app that starts it, and pick Invite Responded as the event. Select your AddCal connection.
- 02
Test the trigger
Run the test. Zapier pulls the three most recent invite replies from the account, so you map fields on a real answer instead of an empty example.
- 03
Add the sheet step
Add an action in your spreadsheet app, then map the reply details from the trigger into the columns of your tracking sheet.
- 04
Add the channel message
Add a second action that posts a short summary to the team channel. This makes the Zap multi-step, so from here on it needs a paid plan.
- 05
Test, then publish
Test each action once and read what came back in the sheet and the channel. When both look right, click Publish to switch the Zap on.
AddCal triggers
2 events start a Zap when something happens in AddCal, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Invite Responded
Instant triggerIn Zapier“Triggers when an attendee accepts, tentatively accepts, or declines a calendar invite.”
Starts a Zap when an attendee answers one of your calendar invites, whether that answer is accept, tentative or decline. It is the trigger for anything that should react to a guest's decision rather than to a sign-up.
New RSVP
Instant triggerIn Zapier“Triggered when a new RSVP is created in any of your events.”
Fires each time someone submits an RSVP on any of your AddCal events, so one Zap can watch every event at once. Each new sign-up becomes the starting point of the steps you add after it.
AddCal actions
AddCal gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Cancel Calendar Invite
ActionIn Zapier“Cancels a previously sent calendar invite by attendee email, sending a cancellation to their calendar.”
Withdraws an invite you already sent, identified by the attendee's email, and pushes a cancellation to that person's calendar.
Create Event
ActionIn Zapier“Create an Event in AddCal”
Builds a new AddCal event from data arriving in the Zap: a title, a start date and an end date are all required.
Create RSVP
ActionIn Zapier“Creates an RSVP response for an event that has RSVPs enabled, including any custom form fields. To email a calendar invite instead, use Send Calendar Invite.”
Records an RSVP answer on an event that collects RSVPs, custom form fields included, as if the guest had filled it in.
Send Calendar Invite
ActionIn Zapier“Sends a real calendar invite (with Yes/No/Maybe) to an attendee by email. For events that collect RSVPs, use Create RSVP instead.”
Emails a real calendar invite with Yes, No and Maybe buttons to one attendee, for an event that has calendar invites enabled.
When an AddCal Zap breaks
Zapier attaches no help article to AddCal, so the traps below come from how Zapier works and from the required fields of the actions.
Most AddCal failures are not errors at all. The Zap runs, but on the wrong event, on nothing, or on itself. Read these four cases before you publish.
Old RSVPs never show up
A Zap only reacts to what happens after it is switched on. RSVPs and replies collected before publishing are not picked up; moving that backlog is a separate job.A Zap that feeds itself
A New RSVP Zap that ends with Create RSVP on the same event sets itself off again and again, and burns through the task count fast.Rejected because the event ended
Create RSVP and Send Calendar Invite both refuse an event that has already ended. A Zap pointed at last month's session fails on every run.A sudden flood held back
If AddCal sends a huge batch at once, after a bulk import for instance, Zapier's flood protection can hold the runs back.
Need help automating AddCal with Zapier?
A person reads every message.
