Log every new SupportCandy ticket in a Google Sheets spreadsheet
Every time a SupportCandy ticket is created on your WordPress site, this workflow adds a row to a Google Sheets spreadsheet with the ticket details you map, giving you a running log outside the helpdesk.
SupportCandy
Google Sheets2 steps Setup ~5 min Used on 893 sites Free to import
What this workflow does
SupportCandy keeps tickets inside WordPress, which is fine for agents but awkward when a manager, a client or a finance colleague wants to look at ticket numbers without a site login. A spreadsheet is easier to share, sort and chart. This workflow builds that sheet for you, one ticket at a time.
The SupportCandy trigger fires when a new support ticket is created. FlowMattic takes the ticket data from that event and passes it to Google Sheets, where the Add New Row action writes it to the spreadsheet and sheet you pick. You choose which ticket values fill which columns.
Nothing here edits a row afterwards. When the ticket is later answered or closed, its row stays as it was, so the sheet records tickets as they looked when they were opened. Each run shows up in Task History with the data that was sent.
Weekly ticket count for a small team
Your support lead sorts the sheet by date each Monday and counts last week's new tickets without opening SupportCandy.
Sharing ticket volume with a client
You run support for a client's site. They get view access to the Google Sheet and see each new ticket logged, with no WordPress account needed.
Spotting repeat topics
Map the ticket subject to a column, then filter the sheet for a product name to see how often the same question comes in.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
SupportCandy Create TicketFires when a new support ticket is created in SupportCandy. The ticket data from that event is passed on for mapping in the Google Sheets step.
- Google Sheets Add New Row
Writes one new row per ticket to the spreadsheet and sheet you choose. Connect your Google account, pick the sheet, then map SupportCandy ticket values to its columns.
What you need
- FlowMatticCore
- SupportCandy AccountAccount
- Google Sheets AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Set up the column headings in your sheet before import, so the Google Sheets step lists them and you can map each ticket value to the right column.
- Add a Filter after the trigger if you only want some tickets logged, for example ones whose subject contains a product name. Test it with a ticket of each kind.
- Add a second action after Google Sheets, such as a chat or email notification, if you also want someone alerted about each new SupportCandy ticket.
Questions about this workflow
Will tickets created before I import this land in the sheet?
No. The SupportCandy trigger reacts to tickets created after the workflow is on. Older tickets stay in SupportCandy only.
Does the Google Sheets row change when a SupportCandy ticket is closed?
No. The workflow adds one row when the ticket is created and never goes back to it. Tracking status changes would take a separate workflow built on a SupportCandy status trigger, if one fits your setup.
Which SupportCandy ticket details can I put in the sheet?
Whatever the Create Ticket event sends. Create a test ticket after import and look at the trigger's data in FlowMattic to see the values available before you map columns.
Does this change anything in SupportCandy?
No. The workflow reads the new ticket event and writes to Google Sheets. Tickets and replies in SupportCandy work as before.
More Support workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted