The Events Calendar Automations
How to Post a Slack Message When a Ticket Is Sold in The Events Calendar
Watching ticket sales by refreshing an orders page is slow and easy to forget. Zapify can post to Slack the moment an order for your event is completed, using the A ticket for an event is purchased trigger and the Send a Slack message action. The Events Calendar and Slack are Zapify PRO integrations.
What this automation does
The automation is one trigger plus one action:
- Trigger: A ticket for an event is purchased (
TEC_TICKET_PURCHASED, The Events Calendar) - Action: Send a Slack message (
SLACK_SEND_MESSAGE, Slack)
When an order for your event is completed, Zapify posts a short message to the Slack channel you choose, with who bought, how many tickets and how much they paid.
PRO feature
The Events Calendar is a Zapify PRO integration. Both the trigger and the Slack action used in this automation need needs an active Zapify PRO licence.
Needs Event Tickets
Attendees, RSVPs, check-ins and ticket orders come from Event Tickets, a separate free plugin from the makers of The Events Calendar. Without it, the trigger stays greyed out in the Zapify builder and says it requires Event Tickets.
One message per order
This trigger runs once for each completed order, however many tickets it holds. An order for four tickets sends one Slack message, not four.
Before you start
- The Events Calendar and Event Tickets installed and active, with tickets sold through Tickets Commerce or WooCommerce (with Event Tickets Plus). RSVPs are free and have no order, so they do not start this automation.
- A Slack app for your workspace with a bot user OAuth token (starts
xoxb-) and thechat:writepermission — see Slack's authentication basics if you are setting one up for the first time. - The bot invited into the channel you want it to post to.
How to build the automation
Step 1: Connect Slack
- Go to Settings → Connections and click Add New.

- Choose Slack, paste in the bot user OAuth token, and name the connection something like Events Slack.

- Save.
See Connections for how this screen works generally.
Step 2: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Announce ticket sales in Slack.

Step 3: Add the "A ticket for an event is purchased" trigger
- Click Add Trigger.

- Choose The Events Calendar as the app.

- Select the trigger A ticket for an event is purchased.

- Configure the trigger:
| Field | Required | What it does |
|---|---|---|
| Event | Yes | Pick the event to watch, or leave it on Any event. The list shows upcoming events and those from the last 90 days; type to search for an older one. |
| Event category | No | Only count events in one category, such as Workshops. Leave it on Any category to include them all. |
Step 4: Add the "Send a Slack message" action
- Click Add Action.

- Choose Slack as the app.

- Select Send a Slack message.

Step 5: Configure the message
| Field | Required | What it does |
|---|---|---|
| Connection | Yes | The Slack connection you set up in Step 1. |
| Channel | Yes | A channel name (#ticket-sales) or ID. The bot must already be a member. |
| Message | Yes | The text to post. Insert the tokens to say who bought what. |
| Post as | No | Overrides the bot's display name for this message. |
For example:
- Channel:
#ticket-sales - Message:
🎟️ {Purchaser name} bought {Tickets in the order} ticket(s) for {Event title} — {Order total}
Step 6: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.

Step 7: Test it
Buy a ticket yourself with a test order. The message should appear in the channel within a minute, or open Zapify → Logs to see what Slack answered.
Tokens you can use
| 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. |
Conclusion
With the A ticket for an event is purchased trigger and the Send a Slack message action, your team sees every sale as it happens without opening the orders screen. To announce the event itself, see posting to Slack when an event is published.
FAQs
Is this free in Zapify?
No. Both the Events Calendar trigger and the Slack action need an active Zapify PRO licence, and Slack also needs a Connection.
Do I need Event Tickets as well as The Events Calendar?
Yes, for anything to do with attendees, RSVPs, check-ins and ticket orders. The Events Calendar only manages the events themselves; Event Tickets is the free companion plugin that adds tickets and RSVPs. Without it, those triggers and actions show as unavailable in the builder.
Can I watch only one event or one type of event?
Yes. Pick the event in the Event field, or choose an Event category to cover every event in it.
Why did Slack say the channel was not found?
The bot has to be invited into the channel first. Type /invite @YourBot in the channel, then run the automation again.
Does it fire for free RSVPs?
No. An RSVP has no order. To react to RSVPs, use the An attendee registers for an event trigger instead.
Do I need to write any code?
No. Everything is configured visually in the Zapify builder.