Resources · Zapier integration

AddEvent Zapier integrationAutomate AddEvent with Zapier.

The AddEvent Zapier integration gives you 2 triggers, 6 actions and 1 search. Both triggers are polling triggers, AddEvent is not a premium app, and the operations cover events, RSVP attendees, calendar subscribers and calendar links. Here is what each one does.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the AddEvent Zapier integration actually does

AddEvent is an add-to-calendar service: it hosts your events, publishes calendars people can subscribe to, and collects RSVPs. Linking it to Zapier works both ways. New subscribers and new RSVP attendees in AddEvent can start work in your other tools, and your other tools can create, update or delete AddEvent events, attendees and subscribers without anyone retyping them.

Three results people usually build. A newsletter list fed by your fixtures calendar. A youth football club publishes its match calendar on AddEvent; New Calendar Subscriber pushes every parent who subscribes into the email tool. Event pages that follow your planning tool. A conference team keeps sessions in a project board, and each change on a card runs Update Event, with Find Event locating the right event first. Personal calendar links in each email. A SaaS onboarding team uses Create Dynamic Add to Calendar Links so every new customer gets a link to their own kickoff call.

What Zapier does not do here: both triggers are polling triggers, so nothing arrives the second it happens. On the free plan, Zapier checks every 15 minutes. There is no trigger for a changed or deleted event either, only for new subscribers and new RSVP attendees. And nothing that existed before the Zap was switched on is picked up.

This site has no n8n or Make page for AddEvent yet. To weigh the platforms, the n8n vs Zapier comparison lists the criteria, and the Zapier review covers the tool itself.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over 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 switched on, Zapier waits for that event to happen.
Action
What the Zap does once it has started: 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.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only unseen ones.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. AddEvent has none of these on Zapier.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Cost

What an AddEvent Zap really costs

Short version: checking AddEvent for new data is free, and every action that goes through costs one task.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger typeBoth triggers polling

The trigger never costs a task, however often Zapier checks. Each successful action counts once, so a three-action Zap uses three times as much as a one-action Zap, and a failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but stops each Zap at two steps: one trigger, one action. Add a second action, a filter or a Find Event search and you have a multi-step Zap (anything beyond one trigger and one action), which needs a paid plan. Both AddEvent triggers follow the interval grid below.

Connect

Connect AddEvent to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an AddEvent account, plus access to any calendar or event you do not own yourself but want the Zap to touch.

  2. 02

    Pick AddEvent

    Type AddEvent in the search box of the dialog, select it from the results, then click Add connection. A new browser tab opens on the AddEvent side, ready for you to sign in.

  3. 03

    Sign in and grant access

    Log in to AddEvent in that tab and allow Zapier to reach the account. The connection is saved, and every AddEvent step in every Zap you build afterwards reuses it.

First Zap

Your first Zap: grow a mailing list from calendar subscribers

GoalA youth football club wants every parent who subscribes to its fixtures calendar added to its email list, then announced to the coaches.

  1. 01

    Create the Zap

    Start a new Zap, choose AddEvent as the app that starts it, and pick New Calendar Subscriber as the event. Select your AddEvent connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent subscribers of the account, so the mapping is done on a real person rather than on an empty sample.

  3. 03

    Add the email list step

    Add an action in your email tool and map the subscriber's details from the trigger into the audience fields, so each parent lands on the club list.

  4. 04

    Add the coaches' message

    Add a second action that posts a short note in the coaches' channel. The Zap is now multi-step, so from here on it needs a paid plan.

  5. 05

    Test, then publish

    Test each action once and read what came back in the list and in the channel. When both look right, click Publish to switch the Zap on.

Triggers

AddEvent triggers

2 events start a Zap when something happens in AddEvent. Zapier checks for them at the interval your plan allows.

1

New Calendar Subscriber

Polling trigger

In Zapier“Triggers when a new subscriber is created on your AddEvent calendar.”

Starts a Zap each time someone subscribes to one of your AddEvent calendars. Whoever follows your published calendar becomes a contact your other tools can use, instead of a name sitting only inside AddEvent.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a theater posting its season calendar wants each subscriber added to its CRM as a warm lead.
Watch out
subscribers who joined before the Zap was published never come through.
2

New RSVP Attendee

Polling trigger

In Zapier“Triggers when a new attendee RSVPs to your AddEvent event.”

Fires when a new attendee RSVPs to one of your AddEvent events. It is the trigger for anything that should happen once a person has said they are coming, such as a welcome message or a seat count.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a coworking space hosting monthly talks logs every attendee in a sheet to plan chairs and coffee.
Watch out
on the free plan a new attendee can take up to 15 minutes to reach the next tool, so do not rely on it for a door list printed at the last second.
Actions

AddEvent actions

AddEvent gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

2

Create Event

Action

In Zapier“Creates a new event on your AddEvent calendar.”

Adds a new event to your AddEvent calendar from data arriving in the Zap, with a required title and start date and time. You can also mark it all day or switch RSVP on.

When to use it
every open day planned in a project board appears on the public school calendar.
Watch out
with RSVP enabled, attendees must RSVP before adding the event to their calendar.
3

Create RSVP Attendee

Action

In Zapier“Creates a new RSVP attendee on your AddEvent event.”

Registers a person on an existing AddEvent event, with their email address and name both required. Reminder emails then go to that address.

When to use it
sign-ups taken at a trade-show booth join the online RSVP list.
Watch out
by default no confirmation or organizer email goes out; turn on Send notification emails if you want them.
4

Delete Event

Action

In Zapier“Deletes an event on your AddEvent calendar.”

Removes an event from your AddEvent calendar for good, as soon as the Zap reaches this step.

When to use it
a session marked as cancelled in your booking system disappears from the published calendar.
Watch out
there is no undo inside the Zap, so test it on a dummy event before pointing it at real ones.
5

Delete Calendar Subscriber

Action

In Zapier“Delete a subscriber from your AddEvent calendar”

Takes a subscriber off your AddEvent calendar. The subscriber to remove is a required field.

When to use it
a member who cancels their club membership in your billing tool stops receiving the members-only fixtures.
Watch out
the earlier steps must identify the exact subscriber, or the action has nothing to delete.
6

Update Event

Action

In Zapier“Updates an event on your AddEvent calendar. Only the fields that you define are updated.”

Changes an existing event on your AddEvent calendar. Only the fields you fill in are touched; everything else stays as it was.

When to use it
a speaker swap or a room change recorded in your planning tool reaches the event page automatically.
Watch out
the event is a required field, so pair this with Find Event when the earlier steps do not carry it.
Searches

AddEvent search

1 search step looks for data that already exists in AddEvent, so a later step can use it.

A search step finds something that already exists in AddEvent and hands it to the next steps. AddEvent has one, listed at the bottom of the action list under SEARCH.

1

Find Event

SearchFind or create

In Zapier“Finds an event in AddEvent with a search term you provide.”

Looks up an event in AddEvent from a search term you give it, so a later step such as Update Event knows which one to change.

When to use it
a festival updates session times from a spreadsheet that only carries session names.
Watch out
the editor also shows Find or Create Events; it is this same search with the create box ticked, not a separate operation.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns the search into a find-or-create: the setting above disappears and Zapier asks for the fields needed to create the missing event.
  3. If multiple search results are found?
    Three ways out when several events match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When an AddEvent Zap breaks

Zapier attaches no help article to AddEvent, so these cases come from how Zapier works and from the fields of the AddEvent actions.

Most AddEvent problems do not show up as errors. The Zap runs late, on the wrong timezone, or silently skips an email you expected. Six cases worth reading before you publish.

  • Old subscribers never arrive

    A Zap only reacts to what happens after it is switched on. Subscribers and attendees already in AddEvent are not picked up; moving them is a separate job.

  • It looks slow

    Both triggers are polling triggers. On the free plan, Zapier checks every 15 minutes, so a new attendee can take that long to show up elsewhere.

  • A Zap that feeds itself

    A New RSVP Attendee Zap that ends with Create RSVP Attendee on the same event sets itself off again and again, and burns through the task count.

  • The wrong timezone

    A timezone written inside the start date is ignored by Create Event and the link action. It has to go in the dedicated timezone field.

  • No confirmation email sent

    Create RSVP Attendee sends no confirmation or organizer email by default. Turn on Send notification emails, and check that the event's own settings allow them.

  • A bulk import held back

    After a bulk import, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.
Need help

Need help automating AddEvent with Zapier?

A person reads every message.

FAQ

AddEvent Zapier integration: frequently asked questions

01Is the AddEvent Zapier integration free?
Yes. AddEvent is not a premium app, so it runs on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. A club pushing new calendar subscribers into one email list fits inside it. Add a second action, a filter or the Find Event search, and the Zap becomes multi-step, which requires a paid plan.
02How many tasks does an AddEvent Zap use?
One task for each action that succeeds, and nothing for the trigger. A Zap that turns each new RSVP attendee into a spreadsheet row uses one task per attendee. Add a chat message and it uses two. Zapier checking AddEvent for new items costs nothing, however often it happens, and an action that fails is not counted against the plan. A few apps elsewhere take more than one task per action.
03Do AddEvent triggers run in real time?
No. New Calendar Subscriber and New RSVP Attendee are both polling triggers: Zapier asks AddEvent for new items at a fixed interval. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans the interval can be changed, and a check can be run by hand from the editor while you build. The type comes from the app and cannot be switched.
04What does it take to connect AddEvent to Zapier?
An AddEvent account, plus access to any calendar or event you do not own yourself and want the Zap to use. The connection takes three moves: open Apps in Zapier, click + Add connection and pick AddEvent, then sign in and grant access in the tab that opens. Before using Update Event or Create RSVP Attendee, make sure the target event exists in AddEvent, since both require it. Without that event, the dropdown stays empty.
05Why does an AddEvent event show the wrong time?
Almost always because the timezone was typed inside the start date. Create Event and Create Dynamic Add to Calendar Links ignore any timezone placed there; it must be set in the separate timezone field of the action. Map that field explicitly, test the step once, and check the result in AddEvent. An all-day event is a different setting and does not need a start time at all. A quick test before publishing catches it every time.
06What if the AddEvent operation you need does not exist?
Then the Zap needs another route. On Zapier, AddEvent offers 2 triggers, 6 actions and 1 search, and no trigger reacts to an event being changed or deleted. Check whether Find Event can fetch the missing value, or whether an existing trigger already carries it. When neither works, a team that builds automations for a living can look at what the AddEvent account itself allows. Most needs fit one of those paths.
07Zapier, Make or n8n for AddEvent?
It comes down to criteria, not to a winner. On Zapier, AddEvent offers 2 polling triggers, 6 actions and 1 search, works on the free plan and needs a paid plan once a Zap passes two steps. Look at which platform your team already pays for, how quickly a new attendee must reach the next tool, and who will maintain the flow. A one-step subscriber sync and a ten-step event pipeline call for different answers.
Same platform

Other docs you might need on this stack.

Browse all integrations