When a Servis.ai webhook fires, add a Google Sheets row and notify the team in Slack
Each webhook event Servis.ai sends becomes a new row in your Google Sheets spreadsheet, and FlowMattic posts a note about it to a Slack channel for the team.
Servis.ai
Google Sheets
Slack3 steps Setup ~5 min Used on 1.9k sites Free to import
What this workflow does
A CRM holds the live pipeline, but managers often want a plain log of what happened and when, plus a quick heads-up when it happens. This workflow gives you both from Servis.ai: a spreadsheet row for each event and a Slack post the team can react to.
Runs start from Servis.ai itself, through its Setup Webhooks trigger, and only for the events you pick there. After import you add the workflow's webhook URL in Servis.ai and pick the events to send, such as deal or contact changes. Every event it delivers starts one run.
The Google Sheets Add New Row step then writes the event to a sheet, and the Slack step posts to a channel. Both ship unmapped: connect your Google account, pick the spreadsheet and sheet, and map the event's fields to your column headers; then choose the Slack channel and write the message, mapping in the details your team should see.
The sheet grows by one row per event, so it becomes a running history you can sort and filter. Run a test event from Servis.ai to see which fields arrive, and use Task History to check each step's result.
Pipeline history for the weekly meeting
A sales manager sorts the sheet of Servis.ai deal events by date before Monday's meeting, while reps see each change in #sales as it happens.
New contacts logged and announced
A services firm sends new-contact events from Servis.ai, so each contact lands in a shared sheet and the team gets a Slack note to follow up.
Reporting outside the CRM
An operations lead builds charts in Google Sheets from the logged Servis.ai events, without giving everyone a CRM seat.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Servis.ai Setup WebhooksFires when Servis.ai sends one of the events you set up in its webhook settings. The event's deal or contact data is passed to Google Sheets and Slack.
- Google Sheets Add New Row
Adds a new row to the spreadsheet you pick for each Servis.ai event. The step ships unmapped: connect Google, choose the spreadsheet and sheet, and map event fields to your columns.
- Slack Send Channel Message
Notifies the team in the Slack channel you choose. Nothing is set yet, so pick the channel and write the text, mapping in details from the Servis.ai event such as the contact or deal name.
What you need
- FlowMatticCore
- Servis.ai 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.
- If your test event carries a date or time field, map it into a column of its own, so you can sort the sheet by when each Servis.ai event happened.
- Put a Filter between the Google Sheets step and the Slack step on a field such as the event type, if every event should be logged but only some should reach Slack. The field is an example to set from your test data.
- Send only the events you care about from Servis.ai's webhook setup, so the sheet doesn't fill with activity nobody reads.
- Swap in Slack's Send Private Channel Message action if the alerts belong in a private sales channel.
Questions about this workflow
Will every Servis.ai change land in my spreadsheet?
Only changes of the types you choose in Servis.ai's webhook setup. Each one it sends adds a row and posts to Slack.
Does an existing row get updated when the same Servis.ai deal changes again?
No. Add New Row always appends, so each event gets its own row. That gives you a history of changes rather than one row per deal.
Do I need column headers in the sheet before importing?
Yes, it helps. Create the headers first, then map the Servis.ai fields to them in the Add New Row step after import.
Can Slack be told only about some Servis.ai events?
Yes. Add a Filter between the Google Sheets step and the Slack step, so every event is still logged but only the matching ones are posted.
More Data Sync 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