Sales Automation #968: NPS Collection with Zendesk + Slack + n8n

Problem

When nps collection depends on hand-offs between Zendesk, Slack, n8n, ownership breaks down and records arrive late in the CRM.

Automating the Zendesk → Slack path keeps the revenue workflow auditable.

Workflow

New or updated record in Zendesk → qualify/enrich → sync to Slack → notify owner in n8n.

Tools Used

• Zendesk
• Slack
• n8n

Setup Steps

1. Connect Zendesk and Slack 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 Zendesk, Slack, n8n.
• 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 Sales.
• Typical implementation complexity: Medium.
• Frees ops time from repetitive nps collection tasks in this stack.

Variations

• Route enterprise accounts to a dedicated owner queue in n8n.
• Require manager approval before updating closed-won records in Slack.

Troubleshooting

• Verify lead owner and account IDs exist on both sides of the sync.
• Check duplicate rules before enabling bi-directional updates.
• Test with won/lost opportunities to ensure terminal stages do not re-open.