When a MoEngage event arrives, log it to Google Sheets, alert the team in Slack, then mark the row processed

Every MoEngage event sent to your FlowMattic webhook is logged as a Google Sheets row, announced in a Slack channel, and then marked processed on that same row using the row number from the first Sheets step.

MoEngage

Google Sheets

Slack

Download this workflow Browse more workflows

4 steps Setup ~8 min Used on 3.4k sites Free to import

The When a MoEngage event arrives, log it to Google Sheets, alert the team in Slack, then mark the row processed workflow on the FlowMattic canvas, with 4 steps across MoEngage, Google Sheets, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

MoEngage tracks how users engage with your app, emails and campaigns. Some of those events deserve a permanent log and a quick word to the team, such as a key conversion or a campaign milestone. This workflow catches the events MoEngage sends to FlowMattic, writes each one to a sheet, posts it to Slack and stamps the row.

The MoEngage Setup Webhook trigger gives you a webhook URL that MoEngage calls when an event occurs. You decide in MoEngage which events are sent there, so send only the ones you want logged. Google Sheets Add New Row then writes the event and returns the new row's number, a Slack message goes to your channel, and Update Row edits the same row through its mapped row number, {google_spreadsheets2.row_number}.

After import, configure the webhook in MoEngage with the URL from the trigger, then send a test event. Map its fields into your sheet columns, pick the Slack channel and write the message, and in Update Row choose the same sheet and set a status column to Processed.

The Processed value is written right after the Slack message posts. Task History shows each event MoEngage delivered and how each step replied.

Log of high-value conversions

A mobile app team sends only its purchase-completed event from MoEngage, so the sheet becomes a running list of in-app purchases with a Slack post for each.

Campaign milestone alerts

A growth marketer forwards a chosen MoEngage campaign event and sees each one in #growth on Slack while the sheet keeps the full history.

Data for ad hoc analysis

An analyst who lacks MoEngage dashboard access works from the Google Sheet of logged events and builds pivot tables from it.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
MoEngage Setup Webhook
Receives the events MoEngage posts to this webhook URL. Choose in MoEngage which events to send here, then send a test event so the fields show up in Task History for mapping.
Step 2Action
Google Sheets Add New Row
Writes each incoming MoEngage event to a new row in the spreadsheet and sheet you pick and returns the row's number. Columns aren't mapped yet, so match the event fields to your headers.
Step 3Action
Slack Send Channel Message
Posts a Slack message about the event to the channel you choose. You write the text after import and map in details from the MoEngage payload, such as the event name.
Step 4Action
Google Sheets Update Row
Marks the row from step 2, found by the row number that step returned, already mapped in the template. Select the same spreadsheet and sheet and set your status column to Processed.

What you need

FlowMatticCore
MoEngage AccountAccount
Google Sheets AccountAccount
Slack 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 webhook in MoEngage for only the events you want in the sheet, so routine activity doesn't fill it and your Slack channel.
Map the MoEngage event name into its own column in Add New Row, so you can sort or filter the sheet by event type later.
If the Slack channel is private, use Slack's Send Private Channel Message action rather than Send Channel Message.

Questions about this workflow

Which MoEngage events reach this workflow?

Only those you set MoEngage to send to the trigger's webhook URL. Pick them in MoEngage when you configure the webhook, and send a test event to see the payload.

How does Update Row target the row for the MoEngage event?

Add New Row returns the number of the row it added, and Update Row uses {google_spreadsheets2.row_number} as its row number, so it edits that row in place.

Will a burst of MoEngage events flood Slack?

Each event runs every step, so every event gets its own Slack message. Send fewer event types from MoEngage, or put a Filter between the first Google Sheets step and the Slack step; that Filter also stops Update Row for those runs.