AI Workflows Automation #4960: NPS Collection with Slack + Google Sheets + Jira

Problem

Model output from Slack is only useful when nps collection results land reliably in Google Sheets with trace logs.

The flow below documents that production path.

Workflow

Webhook or schedule from Slack → business rules for nps collection → write to Google Sheets.

Tools Used

• Slack
• Google Sheets
• Jira

Setup Steps

1. Connect Slack and Google Sheets with scoped API permissions.
2. Configure the nps collection entry condition (Medium difficulty in this library entry).
3. Set field transforms and default values between tools.
4. Add a dead-letter or retry path for failed runs.
5. Validate with sample data before go-live.

Expected Outcome

• nps collection runs without manual copy-paste between Slack, Google Sheets, Jira.
• Status updates stay aligned across the connected tools.
• Failures surface in one place instead of silent drift.

Benefits & ROI

• Ranked as Low ROI in our template dataset for AI Workflows.
• Typical implementation complexity: Medium.
• Frees ops time from repetitive nps collection tasks in this stack.

Variations

• Add a manual approval step before writes to Google Sheets.
• Insert a deduplication check on Slack record IDs.

Troubleshooting

• Add human review for low-confidence classifications.
• Cap token usage and set timeouts on inference steps.
• Version prompts separately from transport logic.