A deal moves to Won. Sales knows. Delivery finds out when someone remembers to send a message.
That gap creates avoidable work. Someone has to find the right checklist, assign the next action, and make sure the client does not wait while the team gets organized.
Ariyel Workflows can turn a record event into a series of actions. A useful first example is the handoff from a won deal to the people responsible for delivery.
Define the handoff before building it
Start with a simple rule: when a deal enters your won stage, start its onboarding fulfillment and create a kickoff task. Use a delivery template you have already reviewed with the team.
Write down the intended deal, template, task, and responsible person before opening the editor. This makes the automation easier to inspect because you know what each action is supposed to accomplish.
If the underlying delivery process is unclear, build that first with Ariyel Fulfillment. Automating an unclear handoff makes the confusion happen faster.
Choose the event and condition
Open Workflows → New workflow and start from scratch in the editor. For this example, choose a field-value-change trigger on Deals and select Stage.
Add a filter for the stage your workspace uses to mean Won. A stage-change trigger on its own would also respond to other stage changes, so the condition gives the workflow its intended scope.
Keep the first workflow focused on one handoff. A broad record-update trigger may run for each supported update, including changes unrelated to the sale. Choose the event that actually signals the work should begin.
Attach the actions to the right deal
Add Start fulfillment and provide the triggering deal and onboarding template. This action needs a particular deal; a contact alone does not tell Ariyel which opportunity you intend to deliver.
Add a task-creation action for the kickoff work, with the relevant record context and assignment. Give it a concrete name, such as “Arrange kickoff and confirm missing assets,” so the next person knows what to do.
Workflows also support conditions, branches, and delays. Add them when your process needs them. A short workflow that handles one repeatable event is easier for the team to understand and maintain.
Publish and check a real run
An owner or admin publishes the configured draft and enables the workflow. Editing the draft later does not change the running version until those edits are published.
Use Trigger workflow on an enabled, published workflow to select an appropriate record and queue a real run. This performs the configured actions. Choose a record on which it is appropriate to create the checklist and task.
Open Runs, select the run, and inspect the individual blocks. Then check the deal, fulfillment, and task themselves. A completed run can have stopped at a filter, so its status alone does not prove that every later action happened.
Keep the process understandable
A failed run does not automatically retry, and actions that already succeeded remain in place. Inspect the outcome before running it again so you can account for any work already created.
Workflow-made changes do not trigger other workflows. Keep dependent actions together instead of expecting one workflow to start a chain of others. For email follow-up, use Enroll in sequence with Ariyel Sequences; there is no direct send-email action.
Review the full Workflows documentation as you configure the handoff. The result should be easy to explain: this event starts this checklist and gives this person the next action.