Task · Workflows

Send attendees to Swapcard or Pipedrive

Send attendee details to Swapcard or Pipedrive when tickets are created or updated.

2 steps · About 5 minutes

1. Connect the service

   You need the owner or admin role in Tito. Open Settings / Connections. For Swapcard, create an organization API token in Swapcard Studio, paste it into Tito, and select Connect.

   For Pipedrive, select Connect next to Pipedrive. Sign in and approve access to your contacts. You’ll return to Tito after connecting.

   go.tito.io/acme/admin/settings/connections

   Swapcard also needs event settings. Open Event Settings / Connections, enter the Swapcard event ID, and save. Tito verifies access to that event. Then map each Tito ticket type to an existing Swapcard group. This mapping is done only through the API: List integration types shows the Swapcard groups, and Replace integration ticket-type mappings saves the map. Create the groups in Swapcard first. Each sync adds the mapped group and preserves existing memberships, including groups added by an earlier mapping.

2. Create and enable the workflow

   Open Settings / Connections. Choose Send attendees to Swapcard or Send attendees to Pipedrive. The workflow is disabled when it is created.

   Review the field mapping, choose the events, and switch the workflow on. To send attendees from before the workflow was enabled, start a backfill from the workflow screen.

Swapcard

Swapcard receives the email address, first name, and last name. Company and job title are optional mappings. First name, last name, and email must all have values.

A profile is created with an account and added to the selected event. When a ticket is voided, the profile is removed from that event. If the email address changes, edit the person in Swapcard, then retry the failed run. The API can’t change that email address.

Swapcard may refuse a profile if its email address is already linked to another profile in the community. Resolve that conflict in Swapcard before retrying.

Pipedrive

Pipedrive finds People contacts by exact email address. A missing contact is created. An existing contact’s name is updated, and its other email addresses are preserved.

If several contacts have the same email address, resolve the duplicate in Pipedrive and retry the run. Contacts are kept when tickets are voided. If the ticket email changes, Tito finds or creates a contact for the new address and keeps the previous contact. No deals are created.

Both workflows retry rate-limit and server failures. Failed runs are recorded in the workflow log.