The Create Approval Task action pauses a workflow until a designated user or group of users reviews and approves it. This is critical when you want human oversight before executing sensitive or high-impact steps, such as updating CRM records, sending external messages, or logging key metrics.
If your team uses Slack, a detailed approval message with task info, fields to review, and Approve/Reject buttons is posted to the selected channel or DM.
If your team uses Microsoft Teams, a simple notification is sent with a link to review and take action in Swyft.
How It Works
Swyft creates an approval task.
Assignees are notified via Slack or Teams.
The workflow automatically includes a “Task Approved?” condition – you don’t need to add this yourself.
The workflow waits until the task is approved or rejected, then continues or follows your rejection path.
Admins can always approve or reject tasks themselves, even if they are not the assigned owner.
Configuration
Task Details
Name - Short identifier for the approval step (for example, “Approve Expansion Deal Data”).
Description - Context so approvers know what they are reviewing. You can include dynamic variables for deal name, ARR, next steps, etc.
Assignees
Static assignment - Select one or more specific users.
Dynamic assignment - Use variables to assign automatically based on context.
Example:
{{user.swyft_user_id}}assigns the approval task to the individual who triggered the workflow.
Notification Settings
Slack - Sends a rich message with task details and Approve/Reject buttons.
Microsoft Teams - Sends a notification with a link to review and act in Swyft.
Fields to Review (Optional)
Add AI-generated insights or workflow outputs that the approver should edit and approve before the workflow continues.
Use this to present generated content like deal metrics, next steps, or competitor mentions for human review.
Best Practices
Use dynamic assignment so the right owner reviews without manual routing.
Reserve approvals for high-impact steps to avoid unnecessary interruptions.
Include sufficient context in the description and fields so approvers can decide without switching tools.
Example Use Cases
Validate AI-generated insights before writing MEDDIC fields to CRM.
Approve high-value deal changes before stage or amount updates.
Pre-send review before posting automation-generated announcements to exec channels.