Log each Emarsys webhook event in a Google Sheets spreadsheet
Each event Emarsys sends to FlowMattic is written as a new row in Google Sheets, so you keep a plain log of the Emarsys events you chose to track, ready to sort, filter and share.
Emarsys
Google Sheets2 steps Setup ~5 min Used on 509 sites Free to import
What this workflow does
Emarsys reports live inside Emarsys. When you need the raw events somewhere else, for a quick analysis, a check on an integration or a teammate without an Emarsys login, a spreadsheet is the most flexible place to keep them. This workflow writes each one to a sheet as it arrives.
The Emarsys trigger is webhook based and fires for the events you specify inside Emarsys. FlowMattic receives each event and passes its data to Google Sheets, where Add New Row adds it to the spreadsheet you choose. You map the event details to columns.
The events you specify decide how fast the sheet grows, so start with the ones you actually need. Different event types may carry different data, so a column can stay empty for some rows. Contact details are personal data; limit who can open the sheet.
Checking an Emarsys setup
While you configure a new Emarsys program, the sheet shows each event as it fires, so you can confirm the right events are being sent.
Sharing data with an analyst
An analyst without Emarsys access works from the Google Sheet, building their own charts from the events you log.
Keeping a simple event history
A small marketing team keeps a running record of chosen Emarsys events in a sheet they can search and filter.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Emarsys Setup WebhookFires for the Emarsys events you specify. Each event's data is passed to the Google Sheets step, one run per event.
- Google Sheets Add New Row
Appends one Google Sheets row for each Emarsys event received. Map the event details to columns; a test event shows which data Emarsys sends.
What you need
- FlowMatticCore
- Emarsys 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.
- If the event data names the event type, map it to its own column, so you can filter the sheet when you log more than one kind of Emarsys event.
- If one event type should go to its own tab, add a Router with a route per event type, using conditions that can't overlap, each with its own Add New Row step.
- Trigger one test event in Emarsys after setup so FlowMattic captures the data, then map the columns before you switch the workflow on.
Questions about this workflow
Which Emarsys events get logged?
The events you specify for the trigger. Every one of them adds a row, so choose only the events you want in the sheet.
Will the Google Sheet fill up quickly with Emarsys events?
It depends on the events you pick and how many your account produces. High-volume events add many rows, so start small.
Can I log different Emarsys events to separate sheets?
Yes. Use a Router after the trigger with one route per event type, each sending to its own spreadsheet or tab.
Does the workflow change anything in Emarsys?
No. It only receives the events and writes rows to Google Sheets.
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