Your event
Integrations
Hold the key a service issued for this event, and tell an account-wide service which of its events this one is.
What you can do here
This page holds the keys for services that issue one per event instead of one for your whole account. Lead retrieval scanners work that way. The key you paste here is used by this event and no other.
Stripe, PayPal and anything else you connect once for the whole account are on Integrations in account settings.
What the key is for
A workflow that sends to one of these services uses the key from the event it ran for. A run for an event with no key fails, and says which service is missing one.
For Validar, Send attendees to Validar covers the whole setup, key and workflow together.
Services the account connected
A networking app is connected once for the whole account, and each event then names its match on the app's side. Its card here takes the organization id and the event id, and lists your ticket types against theirs. Tickets of a type left as Not mapped aren't sent.
Send attendees to Brella covers that setup from the token to the first send.
Good to know
- Your key is encrypted before it's stored, and stays hidden from then on. Keep your own copy wherever the service gave it to you.
- Tito saves a key without checking it. A wrong key shows up as a failed send the first time a workflow runs.
- Each event needs its own key, so a workflow covering three events needs the key on all three.
- Disconnecting deletes Tito's copy of the key. To stop the key working anywhere, replace it at the service.