A precise starting event
Filter Task Status Changed to the status that should begin this workflow.
AMS · Connected business workflows
Build the handoff your team keeps repeating.
Configure supported triggers, conditions and actions with deliberate permissions.
Build the handoff your team keeps repeating.
For operations teams turning a clear process into a configured workflow. Start with an event, add the decision and define the action.
The task is ready. Someone still has to chase the handoff.
Moving work into review is only useful when the next person knows they own it. Repeating the same coordination manually takes attention away from the work itself.
Make the routine explicit, inspectable and repeatable.
When a task enters In review, check whether its priority is High. If it is, assign Layla. Other tasks do not take that assignment path.
Fictional people, records and figures. This example does not change a live workspace.
- The work
- When a high-priority task enters In review, assign it to Layla.
- The people
- A workflow owner configures the rule. Layla is the reviewer chosen for the matching path.
- Where to start
- Use a project with the relevant task statuses, priority values and reviewer. Choose a supported trigger and action.
- Client and brand context
- Client and brand context is optional for this internal handoff. The example rule uses the task’s status and priority; execution still depends on permissions and plan limits.
Follow the work, step by step
Add a trigger
A repeatable handoff starts here.
- What you do
- Drag Task Status Changed from the library onto the canvas. This event is the starting point for the rule.
- What changes
- A Task Status Changed trigger moves from the node library onto the workflow canvas.
- Why it helps
- The handoff begins with a supported event that the team can identify.
The trigger is the first node; it still needs its event settings.
Set the event
Tell the rule when to start.
- What you do
- Set “To status” to In review. This workflow now listens for the handoff that matters, rather than every task update.
- What changes
- The trigger’s To status setting becomes In review.
- Why it helps
- A status filter makes the starting point specific to this review process.
Watch the trigger settings, then the configured node label.
Add a condition
Choose which work follows the rule.
- What you do
- Add a condition: task priority equals High. A matching task follows the Yes branch; other tasks stop here.
- What changes
- A condition checks task priority equals High. Its Yes and No outputs make the decision visible.
- Why it helps
- Only matching tasks should continue to this assignment; other priorities stop on the unconnected No path.
The condition is a branch, not an action that changes the task.
Choose the action
Give the next step an owner.
- What you do
- Add Assign Task and choose Layla. The action is explicit, so your team can understand what will change.
- What changes
- An Assign Task action is added with Layla selected as the assignee.
- Why it helps
- The next responsibility is defined by a person configuring the workflow.
Look for Layla in the action settings.
Connect the nodes
Connect the decision to its outcome.
- What you do
- Join the trigger to the condition, then connect Yes to Assign Task. Review the complete path before enabling it.
- What changes
- The trigger connects to the condition. The Yes output connects to Assign Task; No remains unconnected.
- Why it helps
- You can inspect the exact path before saving, validating and testing the workflow.
Follow the drawn connections and the Yes branch.
Follow the result
Ready for review. Already assigned.
- What you do
- The high-priority task enters review and the configured action assigns Layla. Its brief, deadline and context stay with the work.
- What changes
- The sample run follows the matching path and shows the task assigned to Layla for review.
- Why it helps
- A repeatable handoff can carry the task’s existing context to its next owner.
This is a local demonstration, not a saved or executed live workflow.
What your team gains
A decision you can inspect
Use a condition and its Yes/No branches to control which work continues.
A deliberate action
Choose a supported action and configure exactly who or what it affects.
Prepare your workflow
- Create a workflow in the relevant project and add a supported trigger from the node library.
- Configure the trigger, add the condition and action, then connect their handles in the intended order.
- Review validation, save the workflow and use the available test and execution tools before relying on it.
This page demonstrates local example states. It does not save or execute a workflow. Live execution depends on valid configuration, plan limits and the permissions of the workflow owner.
Understand each tool without leaving this page
Automations — its role in this workflow
- What it does
- The workflow editor connects supported events, conditions and actions into an inspectable rule.
- In this example
- Task enters In review → Priority equals High → Assign Task to Layla.
- What to prepare
- Configure the nodes and their connections, review validation, save and test using the available tools. The tour does none of those things to live data.
Projects — its role in this workflow
- What it does
- The project gives the work a place, a team and a set of tasks. Each task can carry its owner, date and working context.
- In this example
- Keep the Autumn launch creative brief as a task, with Nour responsible for preparation and Layla involved in review.
- What to prepare
- Choose the project team and review process. Moving a task into review does not itself configure an assignment automation.
Permissions & scopes — its role in this workflow
- What it does
- Permissions and scopes determine which records a person can see and which actions they can take.
- In this example
- The workflow owner and reviewer need the access appropriate to the project and the intended assignment.
- What to prepare
- Review the project’s role and scope settings. A diagrammed action does not bypass permissions or execution limits.
Custom fields — its role in this workflow
- What it does
- Custom fields make project-specific details explicit using an appropriate field type.
- In this example
- Collection is text, Launch assets is a number and Review required is a checkbox.
- What to prepare
- Choose the fields that help your team make a decision. A custom value does not enforce a process unless a supported workflow is configured.