Skip to content

The Events Calendar Automations

The Events Calendar and Event Tickets Automations in Zapify: Every Trigger and Action Explained

Running events means a lot of small jobs: thanking people who RSVP, telling the team about a sale, keeping a guest list, following up with the people who came. Zapify PRO connects The Events Calendar and Event Tickets to the rest of your site so those jobs happen on their own. This page lists every trigger and action, what you need installed, and links to eight automations you can copy.

Requirements

PRO feature

The Events Calendar is a Zapify PRO integration. It appears in the free builder greyed out so you can see what it offers before upgrading. See Zapify Free vs Pro.

  • The Events Calendar installed and active. This is enough for the An event is published trigger.
  • Event Tickets installed and active as well, for everything to do with attendees, RSVPs, check-ins and ticket orders. It is a separate free plugin from the makers of The Events Calendar. Without it, those triggers and actions stay greyed out in the builder and say they require Event Tickets.
  • Event Tickets Plus is optional. If you use it, WooCommerce and Easy Digital Downloads tickets work too.

There is no Connection to set up. Both plugins run on your own site, so there is no API key to paste.

Triggers

Trigger Starts when Needs Event Tickets
An attendee registers for an event Somebody RSVPs or buys a ticket. Runs once for each attendee. Yes
An attendee checks in for an event A guest is checked in from the attendee list or by a QR scan. Yes
A ticket for an event is purchased A ticket order is completed. Runs once for each order. Yes
An event is published A new event goes live, optionally in one category. No

Once per attendee, or once per order?

An order for three tickets creates three attendees but only one order. The two triggers differ in exactly this way:

  • Use An attendee registers for an event to act on each guest, such as an email to every person who will be there.
  • Use A ticket for an event is purchased to act on the buyer, such as one Slack message per sale.

Which ticket types are covered

Ticket type Registers Checks in Purchased
RSVP Yes Yes No (RSVPs have no order)
Tickets Commerce Yes Yes Yes
WooCommerce (Event Tickets Plus) Yes Yes Yes
Easy Digital Downloads (Event Tickets Plus) Yes Yes No
PayPal (legacy) Yes Yes No

Actions

Action What it does
RSVP an attendee to an event Reserves a place on an event's RSVP ticket for a person you name, and can send Event Tickets' confirmation email. If a WordPress user has that email, the RSVP is linked to them.
Check in an attendee Marks an attendee as checked in, given the Attendee ID token from an earlier step.

Tokens

Each trigger offers tokens you can insert in any field with a {} button. The attendee triggers share one set:

Token What it holds
Attendee name / Attendee email Who registered or checked in.
Ticket name / Ticket ID Which ticket they hold.
Order ID The RSVP or order the attendee belongs to.
Ticket provider How they registered: RSVP, Tickets Commerce, WooCommerce, Easy Digital Downloads or PayPal (legacy).
Attendee custom fields Any extra questions you ask attendees (Event Tickets Plus), as a ready-to-read list.
Event title / Event URL The event and a link to it.
Event start / Event end When it begins and ends.
Venue name / Venue address Where it takes place.
Organizer name Who is running it.
Event ID / Attendee ID Numeric IDs, for advanced use.

The ticket purchase trigger offers the buyer and order instead:

Token What it holds
Purchaser name / Purchaser email Who placed the order.
Order ID The order number.
Order total How much the order came to.
Tickets in the order How many tickets were bought.
Ticket provider Tickets Commerce or WooCommerce.
Event title / Event URL The event the tickets are for.
Event start / Event end When it begins and ends.
Venue name / Venue address Where it takes place.
Organizer name Who is running it.

The event published trigger offers the event details:

Token What it holds
Event title The event's name.
Event URL The link to the event page.
Event start / Event end When it begins and ends.
Venue name / Venue address Where it takes place.
Organizer name Who is running it.
Event ID The numeric ID, for advanced use.

Ideas to start with

Each of these is a step-by-step page:

Conclusion

The Events Calendar integration lets an event run itself: replies to guests, sales alerts for your team, guest lists, CRM tags and bookings that follow a purchase. Start with the RSVP confirmation email, then explore triggers and actions and filters and conditions to narrow when each one runs.

FAQs

What can Zapify automate in The Events Calendar?

Zapify can react when an attendee registers, when an attendee checks in, when a ticket order is completed and when an event is published. It can also RSVP a person to an event and check an attendee in. Combine those with any other Zapify action, such as email, Slack, Google Sheets, MailPoet or Groundhogg.

Do I need Event Tickets to use the integration?

Only for attendees, RSVPs, check-ins and ticket orders. The An event is published trigger works with The Events Calendar alone.

Is the Events Calendar integration free?

No. It is part of Zapify PRO. The actions you pair it with, such as Send an email, may be free.

Why are some Events Calendar triggers greyed out?

They need Event Tickets, which is a separate plugin. Install and activate it and reload the builder.

Does it work with Event Tickets Plus and WooCommerce tickets?

Yes. Registrations, check-ins and ticket purchases from WooCommerce tickets are covered, and Easy Digital Downloads tickets are covered for registrations and check-ins.

Do I need to write any code?

No. Everything is configured visually in the Zapify builder.

Was this page helpful?