Task · Workflows

Send attendees to HubSpot

Create or update a HubSpot contact as tickets are bought and changed.

4 steps · About 5 minutes

HubSpot keeps the people your marketing and sales work runs on. This adds your attendees to it as tickets are bought and changed, so they're there without an export.

You'll need a HubSpot login with permission to edit contacts.

1. Connect HubSpot

   Open Integrations in account settings. HubSpot is under Other services, below the payment providers. Select Connect, sign in, and choose the account you want Tito to write to. HubSpot asks you to allow access, and sends you back here.

   HubSpot connects the account you pick on that screen.

   If you have more than one, the name you choose there is where every attendee will go.

2. Start from the template

   Open Workflows, select New from template and choose Send attendees to HubSpot.

   Your accountWorkflows

   go.tito.io/acme/admin/workflows

   That creates an ordinary workflow you can edit, already set up to fire when a ticket is bought or changed. It arrives switched off.

3. Check what's being sent

   Open the workflow and look at what it sends. The template sends the attendee's email, first name and last name.

   Email is what HubSpot matches on, so an attendee who already exists is updated rather than added twice. Leave the email line as it is unless you know your HubSpot matches on something else.

   Every other line is a HubSpot property name on the left and what Tito puts in it on the right. HubSpot refuses the record if it's sent a property that doesn't exist, so use the internal name from Settings, Properties in HubSpot when you add one.

4. Turn it on

   Switch the workflow on. It starts with the next ticket.

   To bring across the tickets sold before you turned it on, see Catch up a workflow on tickets already sold.

Good to know

An attendee with no email address can't be sent, because HubSpot has nothing to match on. Those runs fail and say so.

A contact HubSpot already had keeps everything on it. Only the properties in the workflow are written.

HubSpot limits how fast one account can be written to. A busy on-sale can hit that limit, and Tito retries on its own for a few hours before giving up.

If a run fails, the run log has HubSpot's own reply in it, which names the property it objected to.