Zapier connects Eventin to thousands of apps — Google Sheets, Slack, Mailchimp, HubSpot, Twilio — without any code. You create a webhook in Zapier, paste it into your event, and every booking sends the buyer and attendee details straight into your Zap. From there you can log it, email it, or push it into your CRM.
Prerequisites #
- Eventin and Eventin Pro — both installed and active. Zapier is a Pro feature.
- A Zapier account. The Webhooks by Zapier app is a premium app on Zapier’s side, so it needs a paid Zapier plan.
- At least one event with a ticket you can book, so you can test the connection.
Where the settings live #
Zapier is switched on in one place and configured in another. Eventin → Extensions turns the integration on for the whole site. The webhook itself is set per event, under Advanced → Third-Party Integrations on the event you are editing — so different events can feed different Zaps.
Step 1 — Create a webhook in Zapier #
Log in at zapier.com. You can continue with Google or use your email address.
From the Zap workflows dashboard, click Create to start a new Zap.
The editor opens with an empty trigger and action. Click the Trigger step.
Search for Webhooks and choose Webhooks by Zapier as the trigger app.
Open the Trigger event dropdown.
Choose Catch Raw Hook and click Continue. Catch Hook also works — Eventin sends JSON, so Zapier can split it into separate fields for you. Pick that one if you would rather map fields than read the raw body.
Zapier generates a webhook URL that looks like https://hooks.zapier.com/hooks/catch/1234567/abcdefg/. Click Copy and leave the tab open — you come back to it in Step 5.
Step 2 — Turn on the Zapier extension #
In WordPress, go to Eventin → Extensions, find the Zapier card and switch it on. Nothing is sent until this is on, no matter what the event says.
Step 3 — Connect the webhook to your event #
Open Eventin → Events, edit the event you want to connect, and go to Advanced → Third-Party Integrations.
- Turn on “Integrate Zapier”.
- Paste your webhook URL into Zapier Webhook URL.
- Under Send to, tick Purchaser email, Attendee email, or both. Both are ticked by default.
- Click “Update” to save the event.
Step 4 — Make a test booking #
Open the event on your site the way a visitor would. Set a quantity on any ticket and click Get Tickets.
Fill in the billing and attendee details, choose a payment method, and confirm the booking.
The confirmation screen shows the booking ID. Eventin sends the data to Zapier at this moment — when the order is created.
Step 5 — Pull the booking into your Zap #
Back in Zapier, click Test trigger. Your booking appears in the list of caught requests. One booking with a buyer and one attendee arrives as two records, because Eventin sends one request per person.
Open a record to see what Eventin sent. Pick the one you want, click Continue with selected record, then add your action step — a Google Sheets row, a Slack message, a CRM contact — map the fields, and publish the Zap.
What Eventin sends #
Each request is one person, tagged with a record_type of either purchaser or attendee. A booking with a buyer and three attendees fires four times. Use a Zapier Filter or Paths step if you want to treat the two types differently.
Every record carries the buyer or attendee name, email and phone, the event id, title, link and dates, and the order id, status, date and total. Attendee records add the ticket name, ticket price and seat. Purchaser records add the ticket count for the order.
One thing worth knowing: the data is sent while the order is being created, before the payment step finishes. On an unpaid or pending booking the order_status field reflects that early state rather than the final one you later see in Eventin → Bookings. Add a filter on order_status if your Zap should only act on a particular state.
FAQs #
Q: I booked a ticket but nothing arrived in Zapier. What did I miss? #
A: Three things all have to be set: the Zapier card on in Eventin → Extensions, Integrate Zapier on for that event, and a webhook URL saved in the field. The event switch on its own is not enough. Also confirm you clicked Update after pasting the URL.
Q: Only the purchaser came through, not the attendees. Why? #
A: Tick Attendee email under Send to on the event, and make sure attendee registration is enabled in your Eventin settings. Without attendee registration there are no attendee records to send.
Q: The attendee record has an empty email. Is that a bug? #
A: No — Eventin only sends the attendee fields your checkout actually collects. If the attendee form asks for a name only, the email arrives empty. Add the email field to the attendee form on the event and it will be filled in.
Q: Can two events send to different Zaps? #
A: Yes. The webhook URL is stored on the event, so each event can point at its own Zap. Turning the extension on once covers them all.
Q: Should I choose Catch Hook or Catch Raw Hook? #
A: Either. Eventin sends JSON, so Catch Hook gives you ready-made fields to map, while Catch Raw Hook hands you the whole body plus the request headers. Start with Catch Hook unless you need the raw request.
Q: My Zap stopped receiving data after I rebuilt it. #
A: Every Zap gets its own webhook URL. Rebuilding the Zap creates a new one, so copy the new URL into the event and save again.
Q: Will a Zapier outage break my checkout? #
A: No. If the webhook cannot be reached, the booking still completes normally — the failure is logged and ignored, never shown to the buyer.
Conclusion #
Create a Catch Hook in Zapier, switch the Zapier extension on, and paste the URL into your event — that is the whole setup. From then on every booking pushes the buyer and each attendee into your Zap, ready to land in a spreadsheet, an inbox, or your CRM without anyone copying a thing by hand.
