Customer Success Automation #1760: NPS Collection with Slack + Google Sheets + Budibase

Problem

CS teams track nps collection across Slack, Google Sheets, Budibase, but manual updates mean health scores and account notes drift out of date.

This workflow keeps customer records consistent after each lifecycle event.

Workflow

Slack trigger → transform/map fields → Google Sheets action → optional alert via Budibase.

Tools Used

• Slack
• Google Sheets
• Budibase

Setup Steps

1. Create credentials for Slack, Google Sheets, Budibase in your orchestration platform.
2. Define the nps collection trigger in Slack.
3. Map required fields from Slack to Google Sheets.
4. Add error handling appropriate for a Hard workflow.
5. Run a test payload, then enable production execution (~26 min typical setup in our dataset).

Expected Outcome

• A repeatable nps collection path for customer success teams.
• Less context switching between Slack and Google Sheets.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: Medium ROI tier · Hard difficulty · ~26 min setup estimate.
• Reduces manual nps collection steps between Slack, Google Sheets, Budibase.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Variations

• Batch non-urgent nps collection runs on a schedule instead of realtime.
• Archive raw payloads to a datastore for audit.

Troubleshooting

• Exclude churned accounts with an explicit filter node.
• Log CS owner changes when reassigning accounts automatically.
• Re-authenticate OAuth tokens if the flow stops unexpectedly.