Log every Frontly action executed into a Google Sheets spreadsheet
Each time an action runs in your Frontly app, this workflow writes a row to a Google Sheets spreadsheet, giving you a running log you can sort, search and share outside Frontly.
Frontly
Google Sheets2 steps Setup ~5 min Used on 2.4k sites Free to import

What this workflow does
Frontly apps let people press buttons and submit changes that run actions. When something goes wrong, or a client asks who did what, you need a record of those actions somewhere you can read it. This workflow keeps that record in a spreadsheet, one row per action.
The Frontly trigger is Action Executed, which fires whenever an action in your Frontly app runs. FlowMattic passes the data Frontly sends to Google Sheets, where Add New Row writes it to the spreadsheet and sheet you choose. You decide which details go into which column.
Every executed action adds a row, so the sheet grows with use. If your Frontly app also reads from Google Sheets, keep the log in a separate spreadsheet so the two don't mix. Run an action once after import to see which fields Frontly sends.
Client portal audit trail
An agency runs a client portal in Frontly. The log sheet shows when each action ran, which helps answer questions about a change.
Internal tool usage
An operations team built an internal tool in Frontly and wants to see which actions are used most. A pivot table on the log sheet shows the counts.
Debugging a new action
While building a Frontly app, you log each action run to a sheet, so you can compare what was sent with what you expected.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Frontly Action ExecutedRuns whenever an action is executed in your Frontly app. The data Frontly sends about that action becomes available to map into the spreadsheet.
Google Sheets Add New RowWrites one row to the Google Sheets spreadsheet and sheet you pick. Connect your Google account and map each Frontly field you want to keep to a column, such as a timestamp.
What you need
- FlowMatticCore
- Frontly 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.
- Add a column for the time of the run, so the log can be sorted by when each action happened.
- Add a Filter after the trigger if you only care about some actions, for example by a field that names the action. Trigger a Frontly action once and look at the captured data for such a field.
- Use a spreadsheet just for the log, not the one your Frontly app reads from, so log rows never appear inside the app.
Questions about this workflow
Which Frontly actions are logged?
Every action that runs and fires the Action Executed trigger. There is no Filter in the template, so each one adds a row.
What details about a Frontly action reach the sheet?
Only what Frontly sends with the trigger, mapped to the columns you choose. Run one action after import to see the available fields.
Will this log actions that ran before I imported it?
No. Only actions executed after the workflow is switched on are written to the sheet.
More Spreadsheets & Data 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


