Headless 360Intermediateslackflowslash-commandsautomation
Implement Slack slash commands triggering Salesforce Flow via API
Real World Scenario
Support engineers want /create-case Slack command pre-populating Case from thread context but early version created duplicate cases on Slack retries.
Expected Answer
• Verify Slack request signature and timestamp on every slash command invocation
• Use idempotency key derived from Slack team, channel, and trigger_id in Flow entry
• Return immediate ephemeral response while async Flow completes heavy work
• Map Slack user to Salesforce user via linked identity table before case create
• Parse thread context with explicit field confirmation step preventing wrong customer linkage
• Post completion message to thread with Case number link back to Salesforce record
• Monitor duplicate case rate and command error logs for retry storm detection
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Verify Slack request signature and timestamp on every slash command invocation. Use idempotency key derived from Slack team, channel, and trigger_id in Flow entry. Pick based on your integration pattern and team capability. Slack retries are guaranteed—idempotent Flow entry is mandatory, not optional polish. Balance speed of delivery with maintainability.
Architect Perspective
Slack retries are guaranteed—idempotent Flow entry is mandatory, not optional polish.