Log every ended Comm100 chat in a Google Sheets support log
When a Comm100 live chat ends, FlowMattic writes it to a new row in Google Sheets, building a support log you can filter, share with managers or use for weekly reporting.
Comm100
Google Sheets2 steps Setup ~5 min Used on 1.5k sites Free to import

What this workflow does
Comm100 holds your live chat history, but many support leads want a plain list of finished chats next to other team data, or a view for people who do not use Comm100. Exporting by hand every week gets old fast. This workflow adds each chat to your log the moment it closes.
The Comm100 trigger Chat Ended fires when a chat is ended. FlowMattic receives the data Comm100 sends about that chat and passes it to Google Sheets, where Add New Row appends it to the spreadsheet and sheet you select. You choose which chat details fill each column.
One ended chat makes one row. The workflow never edits or removes rows, so the sheet grows as a running history. Comm100 itself is not changed. If a row looks wrong, Task History shows the data the trigger received and what was sent to Google Sheets.
Weekly chat volume report
A support lead counts rows per day in the sheet to see when chats peak and plans agent shifts around it.
Review queue for quality checks
A team lead adds a column for review notes beside each logged chat and works through a sample of ended chats every week.
Sharing chat activity with sales
The sales team reads the support log in Google Sheets to see which prospects chatted recently, without needing a Comm100 seat.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Comm100 Chat EndedFires when a chat ends in Comm100. The details Comm100 sends about the finished chat are passed on so you can map them into columns.
Google Sheets Add New RowWrites a new row to your support log in Google Sheets for every ended chat. Connect your Google account, pick the spreadsheet, and map Comm100 fields to columns.
What you need
- FlowMatticCore
- Comm100 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.
- End a test chat in Comm100 after import so FlowMattic captures a sample. Map from that data to see which chat details are available.
- Agents often add wrap-up details after a chat closes. Comm100's New or Updated Chat Wrap-Up trigger can feed a second workflow if you want those notes logged too.
- Keep a couple of unmapped columns beside the logged chat data for reviewers' comments. FlowMattic writes only to the columns mapped in the step, so those notes stay untouched.
Questions about this workflow
Does every ended Comm100 chat get its own row?
Yes. The Chat Ended trigger fires once per chat and the Google Sheets step adds one row each time.
Will the full chat transcript be in the sheet?
Only if Comm100 sends it with the Chat Ended event. Run a test chat and check the captured data to see what you can map.
Are chats that ended before I imported this added to the log?
No. The workflow logs chats that end after it is switched on.
Can two Comm100 chats ending at once cause a problem?
Each chat starts its own run and adds its own row, so both are logged. Task History lists each run separately.
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