Connect Ticket Tailor so that the people who buy tickets and come to your events are recorded in ThirdSectorBee, with their ticket payments and check-ins linked to a fundraising activity. For what each Ticket Tailor record becomes, see Ticket Tailor sync behaviour.

Before you start

  • Ticket Tailor must be switched to Enabled on the Integrations overview. See enable a service first.
  • Saving the API key, the signing secret and event mappings needs tickettailor:settings:change. Starting a sync needs tickettailor:sync:initiate.
  • Have access to your Ticket Tailor box office settings, to create an API key and a webhook.
  • Decide which fundraising activity each event belongs to. You can create activities first, or have one created for an event.

Connect your account

  1. In Ticket Tailor, create an API key in your box office settings.
  2. In ThirdSectorBee, open Integrations → Ticket Tailor. The Settings tab opens.
  3. Paste the key into API key and choose Connect Ticket Tailor.

ThirdSectorBee checks the key with Ticket Tailor before saving it. If Ticket Tailor refuses it, you’ll see that Ticket Tailor did not accept the key, and nothing is saved. Once connected, the page header shows Connected. The key is never shown again; to replace it, paste a new one and choose Update API key.

Set up the webhook

Without a webhook, records still arrive through the hourly check. A webhook makes new orders and tickets arrive within moments. Once you’re connected, the Settings tab shows the steps:

  1. In your Ticket Tailor box office settings, add a webhook.
  2. Use the Webhook URL from the Settings tab (choose Copy).
  3. Choose the events Order created, Order updated, Issued ticket created and Issued ticket updated.
  4. Save the webhook. Then, in Ticket Tailor, choose Show signing secret, copy it, paste it into Signing secret in ThirdSectorBee and choose Save signing secret.

The Settings tab then shows Signing secret saved. Until it does, every webhook delivery is refused. If a delivery is refused (for example because the signing secret was pasted wrongly), the Settings tab says so, with when it happened and why, and Ticket Tailor shows the delivery as failed in its own webhook log.

Map each event to a fundraising activity

Nothing is imported for an event until it’s mapped.

  1. Open the Mappings tab. It lists your Ticket Tailor events with their Date.
  2. For each event you want to import, choose under Import:
    • Create activity, and check the name (it starts as the event’s name), to have a fundraising activity of that name created with the activity type Event, or
    • Link to existing activity, and choose the activity.
  3. Leave Not imported on events you don’t want in ThirdSectorBee.
  4. Choose Save mappings.

To stop importing an event, set it back to Not imported and save. These mappings link Ticket Tailor events to fundraising activities. They don’t create records in the separate Events module.

When records arrive

  • Every hour, ThirdSectorBee checks Ticket Tailor for new tickets, orders and check-ins on each mapped event, until 30 days after the event ends. This is the only route for check-ins.
  • Within moments, once the webhook is set up, for new and changed orders and tickets.
  • When you ask. Choose Sync now on the Settings tab for every mapped event, or Sync this event on a row of the Mappings tab. A sync you start also covers events that ended long ago. It runs in the background: the Settings tab shows it running, then when it finished and what it did.

Running a sync again is safe. A ticket, order or check-in already imported is skipped unless it changed in Ticket Tailor, so it never creates duplicate payments or touchpoints.

What it creates

From Ticket Tailor In ThirdSectorBee
Issued ticket The ticket holder as a contact, matched or created by email address, with a [Ticket Tailor] Ticket issued touchpoint
Completed order The buyer as a contact, and a Paid, inbound payment with the payment method Ticket Tailor, linked to the activity
Check-in A [Ticket Tailor] Checked in touchpoint on the ticket holder’s contact, linked to the activity

Enabling Ticket Tailor adds those two touchpoint types and the Ticket Tailor payment method to your beehive. It doesn’t record consent: a ticket purchase doesn’t tell ThirdSectorBee whether someone agreed to hear from you, so check their consent separately before contacting them. Nothing is sent back to Ticket Tailor.

The History tab

The History tab lists the last 90 days of webhook deliveries, syncs you started, and hourly checks that imported something, newest first. Each row shows when it happened, where it came from (Webhook, Hourly check or Manual sync), the Ticket Tailor event for a delivery, whether it was Processed, Skipped or Failed, and why or how many records it covered. Choose Load more for older rows.

If something goes wrong

What you see What to do
Ticket Tailor did not accept the API key Check the key in your Ticket Tailor box office settings and that it belongs to the right box office, then paste it again
Ticket Tailor could not be reached Try again in a few minutes
A webhook delivery was rejected Choose Show signing secret in Ticket Tailor again and paste it into Signing secret. If it says the signature was too old, check the delivery wasn’t held up and resent much later
A sync is already running Wait for it to finish; the Settings tab shows its progress
An event’s records never arrive Check the event is mapped on Mappings, then choose Sync this event
A payment is missing Only completed orders become payments, and a free order brings in the buyer but no payment. Check the order’s status in Ticket Tailor
A refunded order still shows as paid A refund made after the order was imported isn’t reversed by the integration. Update the payment in ThirdSectorBee