Solutions engineer assignment approval with CRM validation and Slack routing
Build a Solutions Engineer (SE) assignment approval workflow for inbound sales requests, scoped to a specific set of regions (I used EMEA and ANZ) so that requests outside that scope are left untouched for our existing process. Trigger it with an inbound webhook route that receives POSTs from our existing SE Assignment intake form — keep that form as the front door rather than replacing it. The workflow should acknowledge the submission immediately and do its work downstream. At a high level, the workflow should: Receive the form submission, pull out the reference to the relevant sales opportunity, and pass a clean payload downstream. Validate the request against our CRM — look up the opportunity (name, stage, account, owner, region), decide whether it's in the target region scope, and apply a stage gate so only opportunities at or beyond a configurable starting stage proceed. Read the stage list live from the CRM so the gate stays in sync automatically. This lookup should be read-only. For in-scope requests, ask a designated approver to pick an SE — store the request context durably, then send the approver a message with one button per assignable SE. If the stage gate fails, send the approver a heads-up instead. Out-of-scope requests should stop silently. Handle the approver's button click via a second webhook route — notify the chosen SE and the opportunity owner (AE) with a link to the opportunity, update the approver's original message, and clear the stored context. Use a CRM connector for the opportunity and stage lookups (I used Salesforce — or your team's CRM) and a chat tool for the approval prompt, the interactive buttons, and the SE/AE notifications (I used Slack — or your team's chat tool). Keep an editable roster of assignable SEs and a configurable approver and starting stage. Note that after publishing, the intake form's outbound webhook and the chat app's interactivity settings need to be pointed at the two published route URLs. Tools used: Salesforce (read-only REST API), Slack (chat:write, users:read.email), Tines SE Assignment intake form (inbound webhook), persistent named volume for request context
What this prompt builds
An approval workflow that validates inbound Solutions Engineer assignment requests against CRM opportunity data and regional rules, then routes qualified requests to an approver who selects an SE from an interactive list in Slack. The workflow bridges an existing intake form, Salesforce opportunity lookups with configurable stage gates, and Slack-based approval and notifications, reducing manual context-switching across tools. Currently read-only; it does not write the final assignment back to Salesforce.
The problem
Sales teams managing Solutions Engineer assignments across multiple regions face friction when validating requests against CRM opportunity data and coordinating approvals. Manually checking opportunity stage, region, and account details in Salesforce, then assigning SEs and notifying stakeholders across Slack and the CRM, creates delays and scattered context. This workflow automates the validation, routes in-scope requests to an approver with an interactive Slack picker, and notifies the chosen SE and the account owner—all triggered from an existing intake form and governed by configurable region scope and stage gates read live from Salesforce.
Solution and impact
The workflow eliminates manual lookups and context-switching by automatically validating assignment requests against live CRM data, filtering by region and opportunity stage, and delivering actionable approval prompts directly in Slack. Approvers select an SE with a single button click, and the workflow immediately notifies both the assigned SE and the account executive with a link to the opportunity. Teams save time on each assignment, reduce errors from manual checks, and keep the approval process centralized and auditable without replacing their existing intake form.