Operations Automation #2574: NPS Collection with Salesforce + Slack + Intercom

Problem

Internal nps collection spans Salesforce, Slack, Intercom, yet ops still copy payloads between systems to keep processes moving.

Central orchestration reduces single points of failure and tribal knowledge.

Workflow

Event in Salesforce → validate payload → update Slack → log outcome for review.

Tools Used

• Salesforce
• Slack
• Intercom

Setup Steps

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

Expected Outcome

• A repeatable nps collection path for operations teams.
• Less context switching between Salesforce and Slack.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: High ROI tier · Medium difficulty · ~31 min setup estimate.
• Reduces manual nps collection steps between Salesforce, Slack, Intercom.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Troubleshooting

• Inspect execution logs for HTTP 429 rate-limit responses.
• Run a single test record before bulk backfill.
• Pause the workflow before rotating API keys, then resume after credentials update.