AI Workflows Automation #4974: NPS Collection with Salesforce + Slack + AWS S3

Problem

AI-assisted nps collection needs guardrailed hand-offs from Salesforce to Slack so humans can review edge cases.

This pattern separates inference, routing, and downstream action.

Workflow

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

Tools Used

• Salesforce
• Slack
• AWS S3

Setup Steps

1. Create credentials for Salesforce, Slack, AWS S3 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 Hard workflow.
5. Run a test payload, then enable production execution (~44 min typical setup in our dataset).

Expected Outcome

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

Benefits & ROI

• Library metadata: Low ROI tier · Hard difficulty · ~44 min setup estimate.
• Reduces manual nps collection steps between Salesforce, Slack, AWS S3.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Troubleshooting

• Log model inputs/outputs for traceability; never send secrets to LLM nodes.
• Add human review for low-confidence classifications.
• Cap token usage and set timeouts on inference steps.