AutomatorWP - The Events Calendar

Your purchase list also holds people who never showed up

Your workshop ends and you want to send the material to attendees, open a course for them or give them a reward. The list at hand is the purchase list, and it also holds whoever paid and never appeared. Buying and attending are two different facts, and your follow-up changes depending on which one you listen to.

AutomatorWP The Events Calendar connects those moments of an event with the rest of your WordPress plugins. Each one can start an automation, so what happens after confirming, buying or reaching the door can be different.

The event moments you can listen to

This integration offers five triggers. The first carries the FREE label and the other four, PRO:

• A user confirms their RSVP for an event.
• A user purchases a ticket for an event.
• A user purchases a ticket for an event in a category.
• A user checks in at an event.
• A guest confirms their RSVP for an event.

The category version helps when you run a family of events and want the same response for all of them.

AffiliateWP, LearnPress and the action that signs people up

The sample automations show the usual route: a ticket purchase that adds a referral in AffiliateWP, or an RSVP to a specific event that enrolls the user in a LearnPress course.

It also works the other way around. The PRO action RSVP user to an event signs a user up for an event, and you can hang it from another integration's trigger. If that combination suits you, test it first with a trial account.

The guest without an account needs a different setup

AutomatorWP separates automations for logged-in users from anonymous ones. Anonymous automations accept a single trigger, and their list narrows to the ones designed for that type. They also include a selector that decides which account receives the actions: an existing user or a new one. If it finds no match, you can choose not to run the actions.

It is worth deciding this before publishing the event, because that option determines what happens to someone who confirms without an account.

AutomatorWP, The Events Calendar and your first automation

It is an add-on: it needs AutomatorWP and The Events Calendar. It does not handle RSVPs, ticket sales or check-in itself either; it only reacts to what already happens in your ticketing system. Event Tickets is the piece of that family that covers those tasks. This is how the first automation is built:

1. Go to AutomatorWP, Automations, and click the button to add one.
2. Choose the automation type and confirm.
3. Add the event trigger under "When this happens".
4. Add the task under "Do this".
5. Review Times per user: it defaults to 1, so a user completes the automation only once. If your attendees come back and it must always run, set it to 0.

When your automation goes beyond the calendar

AutomatorWP Pro is the starting point for adding more integrations, such as WooCommerce, LearnDash or Mailchimp. To send event data to an external service, AutomatorWP Webhooks sends and receives data with applications compatible with webhooks or a REST API.

If you prefer another engine, Uncanny Automator Pro works with recipes and supports scheduled delays, loops and conditional branching. To extend the calendar or the tickets there are The Events Calendar Pro and Event Tickets Plus.

Purchases, check-ins and repeats, case by case

Can I respond differently to buyers and attendees?

Yes, because purchase and check-in are separate triggers. One automation for each is enough.

Does it work for one specific event only?

The samples include an RSVP to a specific event and a purchase for any event. There is also a purchase trigger by category.

Does it record the check-in at the door?

This add-on does not. Your ticketing system handles that record, and the trigger reacts when it happens.

Can I sign someone up for an event from another action?

Yes, with the PRO action RSVP user to an event, which is part of this integration.

Does it repeat if a member attends several events?

That depends on Times per user. With the default value of 1 it completes once; with 0 there is no per-user limit.