Integrations
Connect QuickBooks Online, Google Sheets, Slack, Telegram or Discord, HubSpot or Mailchimp, or your own server through a webhook. Ticket orders, RSVPs, registrations, volunteer shifts and sponsor applications go out automatically, shortly after they happen, each payment lands in your books, and no one exports a spreadsheet to keep it current.
A Pro account connects up to two tools, a Business account up to five; owners and admins set them up under Library › Integrations.
Sale and RSVP notifications
Front of house sees each sale as it lands: who bought, which tickets and for which date, a volunteer’s shifts, a sponsor’s package, and a link back to the event. Every message uses that chat’s own formatting, and nothing a guest types can ping the whole channel.
CRM and email lists
The buyer, the guest who replied, the volunteer, the sponsor or vendor with their organization, the donor and the member are created or updated by email, with their address and a note saying how they came: the event, its date and what they bought or answered.
Accounting
Connect your company and match your GL codes to its accounts once. From then on each payment, whether by card, in person or entered by hand, becomes one sales receipt with a line per item and its tax. What Stripe kept is a journal entry apart, which leaves the deposit account equal to the payout.
Spreadsheets
Share a spreadsheet of yours with the address we show and paste its link. Each buyer, guest, volunteer, partner, gift, member and sign-up then gets a row on a tab of its own, beside the event’s name and start. A change rewrites that same row: a check-in fills Checked in, a refund fills Last refund, and nobody appears twice.
Webhooks, Zapier and Make
Point it at your own server, a spreadsheet script, or a Catch Hook in Zapier or Make, where no code is needed. Each request is signed the Standard Webhooks way and carries the same id on every retry, so a receiver can safely ignore a repeat.
What can be sent
Tick whole groups, single happenings, or Everything, which includes kinds added later. Cover all your events, or just one.
An order paid, refunded wholly or partly, or a ticket cancelled without a refund.
A new reply, a changed one (yes, no or maybe, the party, the answers), and a guest removed.
A guest or ticket admitted, or leaving again, with the date on repeating events.
Shifts someone took, and each one approved, declined or withdrawn.
An application, its decision, the package paid, and any refund.
A gift received or refunded, and a membership bought or renewed.
Items bought through your sign-up lists, then any refund.
Each payment once it is final, with its lines, tax and the fees taken out, booked in QuickBooks or sent by webhook to another bookkeeping tool.
Built to be relied on
Each one is recorded with the sale itself and sent a moment later, so no buyer waits on your tools.
A tool that is down gets about a day and a half of retries. If it keeps failing, or says the connection is gone, it is switched off and owners and admins get an email.
Thirty days of what was sent and what came back, filtered by state. Resend one, or everything that failed.
Try a new connection before real sales arrive: a test message or ping, a look at your list or QuickBooks company, or the tabs added to your spreadsheet.
Cover all events plus the organizer page, or a single event, which can also opt out of an account-wide one.
Tokens, keys and chat addresses are stored encrypted and never shown again once saved.
Getting started
Owners and admins find it in the Library, or in one event’s settings for that event alone.
Each shows its own fields and the few steps to get its key or address. QuickBooks has you sign in at Intuit; Google Sheets, share the spreadsheet with us.
All events or one, and the groups of happenings it should receive.
Then leave it on, and watch each delivery arrive in the log.
Questions
Pro connects two and Business five. Every integration counts, whatever its kind and whether it is on or off, and deleting one frees its place. Free has none. If you move back to Free, your integrations and their log stay readable, but nothing is sent or changed until you upgrade again.
No. Every tool except a webhook connects from a short form with the steps beside it: you sign in at Intuit, share a spreadsheet, or paste a key or channel address. Only a webhook aimed at your own code needs a programmer, and Zapier or Make can receive one without any.
No, one way: from EventsMagic to your tool. Edits made in QuickBooks, a spreadsheet, a CRM or a chat are never read back, so changing a row or a contact there leaves your event untouched.
Yes, through a webhook. Paste the Catch Hook address from Zapier or Make, choose Everything, and each happening arrives there as data you can pass on to any app those services reach. No code is needed.
The person who registered: a buyer, a guest who replied, a volunteer, an applicant with their organization, a donor or a member. Refunds, check-ins and changes add nobody, and neither does an anonymous gift. Other ticket holders join only if you switch that on, and only those with their own email.
Not by default. Our forms ask for no marketing consent, so new people join your audience as contacts only. You can have Mailchimp email them to confirm, or subscribe them when you have their consent. Anyone already in the audience keeps their own choice.
QuickBooks Online. You sign in at Intuit, choose your company, then pick the deposit and income accounts, the tax codes and an account for each GL code. Payments made after that are booked; earlier ones are not sent. If something is missing, such as a GL code with no account, the log says so, and Resend writes the record once it is set.
No. A retried delivery never writes a second record, and a card sale waits until Stripe’s actual fee is known, so your books match the payout to the cent.
A tab per kind of record you chose: Buyers, Ticket holders, Guests, Volunteers, Partners, Donations, Memberships or Sign-ups. Each starts with an ID column, then the event and when it starts. Rows are found again by that ID, so you can add columns of your own or move ours; only ID must stay first.
In Google Sheets, when you ask. New records are written as they happen, in small batches that stay within Google’s limits; Write what is already there adds the earlier ones as a background job, and Stop ends it. Running it again updates rows instead of adding them twice. QuickBooks books only payments made after you connect.
Everyone in the chat reads what is posted, so each chat integration has Leave out contact details: names and tickets stay; phone numbers and email addresses go. A webhook always carries the full details, since it reaches a system you run.
Each delivery is retried for about a day and a half. If the tool keeps failing for three days, or tells us the connection is gone, the integration is switched off and your owners and admins get an email. Nothing is lost meanwhile: once it is fixed, resend everything that failed from the log.
Yes. Add an integration from that event’s settings and it hears only about that event. An account-wide integration can also be turned off for any single event.
Try it on your next event
Build the event on Free, then move to Pro when you are ready to connect the tools you already use.