Task · Workflows

Add attendees to a Google spreadsheet

Add a row to a Google spreadsheet as each ticket is registered.

5 steps · About 4 minutes

You'll need a Google account. We make the spreadsheet itself, so there's nothing to set up in Google first.

1. Connect Google

   Open Integrations in account settings. Google Sheets is under Other services, below the payment providers. Select Connect, choose your Google account, and allow access.

2. Create the spreadsheet

   On the Google Sheets card, select Create a spreadsheet. Tito makes one in your Drive named after your account and writes to that from then on. Select Open in Google Sheets to see it.

   Tito writes to the spreadsheet it made, and can't open anything else in your Drive.

   That's the narrowest access Google offers, and it's why there's a button here instead of a box to paste a spreadsheet address into. A spreadsheet you already have isn't one Tito can add to.

3. Start from the template

   Open Workflows, select New from template and choose Add attendees to a Google spreadsheet.

   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 registered and pointed at the spreadsheet you just made. It arrives switched off.

4. Check the columns

   Open the workflow and look at what it sends. The template writes five columns: the ticket reference, the attendee's name, their email, the ticket type, and the event name.

   The order of the columns is set in the workflow, so add a heading row yourself if you want one. Changing a column means changing both the list of columns and the fields above it.

5. Turn it on

   Switch the workflow on. The next ticket adds a row.

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

Good to know

Rows are added at the end of the sheet. Nothing already in it is overwritten.

Values are written as text, so a name beginning with = stays a name instead of becoming a formula.

The same ticket run through twice adds two rows. A spreadsheet has nothing to match on, so this is a record of what happened rather than a list that keeps itself tidy.

Google limits how fast a spreadsheet 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.

Renaming or moving the spreadsheet in Drive is fine. Deleting it isn't, and the runs fail until you create another one and point the workflow at it.