Create and update events, and react to RSVPs, ticket sales and check-ins.
Triggers and actions
Every step The Events Calendar adds to FlowWP, named and described as it appears in the editor, with the plan that includes it.
Events in The Events Calendar that can start a workflow.
The first time it goes live, however it was created — the editor, an import, or a workflow.
Event
One run per attendee, so an RSVP for three people runs three times. Optionally only one event.
Attendee
Event
User
A paid ticket through Tickets Commerce, once per attendee. Optionally only one event.
Attendee
Event
User
At the door, however the check-in was made. Optionally only one event.
Attendee
Event
User
Someone was marked as arrived and then unmarked — usually a correction at the door.
Attendee
Event
User
Optionally only the first time it is created.
Venue
Change
Optionally only the first time it is created.
Organizer
Change
A ticket or RSVP being saved, with what is left of its capacity. Optionally only one event.
Ticket
Event
What a workflow can do in The Events Calendar.
Adds an event to the calendar, optionally at a venue and with an organizer.
Event
Changes only the fields you fill in; anything left blank stays as it is.
Event
Moves it to the trash, where it can be restored, unless you ask for it to be deleted outright.
Event
Adds a venue events can then be held at.
Venue
Adds an organizer events can then be run by.
Organizer
Adds them as an attendee on an RSVP ticket, as though they had answered themselves.
Attendee
Event
Marks them as arrived, as the door app would. By attendee ID, or by email for an event. Needs Event Tickets.
Attendee
Marks them as not arrived again. By attendee ID, or by email for an event.
Attendee
Checks, lookups and helpers that shape the data in between.
Fill in what matters and leave the rest blank. Use the False branch for “is not”.
Event
By email address. Use the False branch for “is not registered”. Needs Event Tickets.
Attendee
How many places are still available, across the event’s tickets or on one of them.
Event
How many events they registered for, or actually turned up to, in the last so many days.
The Events Calendar steps run inside WordPress, on your own server. FlowWP only contacts an outside service when you add a connection to one or use a step that needs it.
Nothing runs until you activate a workflow, and every run is recorded step by step.
Templates
Trigger: An event is published (The Events Calendar)
Action: Ask AI (AI)When an event is published, AI writes a short announcement from its own details — date, place and description — and it lands with whoever sends the newsletter.
Trigger: Someone RSVPs to an event (The Events Calendar)
Action: Add or update a MailPoet subscriber (MailPoet)Action: Add tags to a subscriber (MailPoet)Someone RSVPs, gets a confirmation with the date and the address, and joins a MailPoet list tagged as an attendee so you can write to them before the day.
Trigger: An attendee checks in (The Events Calendar)
Action: Add tags to a contact (Groundhogg)A day after someone is checked in at the door, they are thanked — and a Groundhogg tag marks them as somebody who comes, not just somebody who registers.
Trigger: Someone RSVPs to an event (The Events Calendar)Condition: An event has tickets left (The Events Calendar)Every RSVP checks what is left. When the event is down to its last few places, someone hears about it while there is still time to add capacity.
Start with a template or a blank canvas. Nothing runs until you activate it.
