Log Gorgias Support Tickets to Google Sheets Automatically

PromptCreate

On a cron schedule every hour, pull the newest Gorgias support tickets and append every new one as a row in a Google Sheets tracking tab, so the team has a running log for reporting and backup.

Fetch tickets with the Gorgias List Tickets operation, filtered to tickets created since the last run (order_by created_datetime:desc and filter on created_datetime against a stored high-watermark of the most recent created date already logged). Gorgias is not a poll provider, which is why this runs on cron plus List Tickets rather than a poll trigger.

Before writing, read the existing ticket ID column from the tracking tab with the Google Sheets Get Values operation and build a set of IDs already present, so tickets are deduped on ticket ID and never appended twice across runs (the created_datetime filter narrows the fetch; the ID set is the source of truth for dedupe).

For each new ticket whose ID is not already in the sheet, map a fixed set of fields into one row in this column order: ticket ID, created date, subject, channel, requester email, status, tags (comma-joined), and assignee. Write the rows into the tracking tab with the Google Sheets Append Values operation, one row per new ticket.

Keep it fully deterministic: a fixed column mapping, one row per ticket, no summarizing or judgement. If there are no new tickets since the last run, do nothing. Build this as a code workflow.

What does this prompt do?

Checks Gorgias every hour for new support tickets and adds each one to a Google Sheets tracking tab.
Records the key details for each ticket: ID, created date, subject, channel, requester email, status, tags, and assignee.
Skips tickets that are already in the sheet, so you never get duplicate rows across runs.
Gives you a searchable, shareable backup of your support history for reporting.

What do I need to use this?

A Gorgias helpdesk account.
A Google account with a Google Sheet to log tickets into.
A spreadsheet tab with a header row for the columns you want to track.

How can I customize it?

Change how often it runs, for example every 15 minutes or once a day.
Adjust which ticket details get logged, or the order of the columns.
Point it at a different spreadsheet or tab.

FAQs

Will this create duplicate rows if it runs often?

No. Before adding anything, it checks the ticket IDs already in your sheet and only adds tickets that are not there yet.

How often does it check for new tickets?

By default it runs once an hour, but you can set it to any schedule you like, from every few minutes to once a day.

What details get saved for each ticket?

Ticket ID, created date, subject, channel, requester email, status, tags, and the assigned agent, one ticket per row.

Do I need to set up the spreadsheet first?

Yes. Create a Google Sheet with a tab and a header row, and the workflow appends a new row for each ticket underneath.

What happens if there are no new tickets?

Nothing. If there is nothing new since the last check, the workflow simply does nothing that hour.

Related templates

Call overdue Xero customers with an AI collections agent

Every weekday at 10am, an AI voice agent phones your most overdue Xero accounts, logs what each customer promised, and reports back to finance in Slack.