Workflow recipes
These examples are configurations to build in the editor. Object and field names are examples: use supported objects and actual choices from your workspace. Test with recognizable records and inspect the resulting run before enabling a workflow for routine use.
Follow up on a new requestโ
Record created โ Create Task โ End
Use a supported custom request object and read access to the resulting Tasks. Select that object on the trigger, give the Task the title Review: [record display name], choose an assignee if needed, and link the triggering record.
Preview against a sample record. Publish, then create a new record. Verify a successful run, the resolved title and the Task's record link. Existing records are not backfilled. The first-workflow guide walks through this example in detail.
Act when a status changes to a particular valueโ
Record updated โ If/Else โ Create Task or End
Use an object with a status field supported by the trigger's field and comparison selectors. Watch that field in the update trigger. Configure If/Else to compare its captured value with the actual review-needed choice/value offered for that field. Connect the matching path to a linked review Task and then End; connect the otherwise path directly to End.
Verify two changes: one to the review-needed value should create a Task; one to a different value should finish successfully without that Task. An update to an unrelated field should not match the changed-field trigger. Preview alone cannot verify the before/after event match.
Approve work, with an explicit expiry pathโ
Manual record โ Ask Question (Approval preset) โ one answer path
Choose a supported request object and an assignee for the question. Set Wait up to to one day. Connect Approve to Create Task Prepare request, Reject to End, and No answer in time to Create Task Review unanswered approval followed by End. Connect the approved Task to End too. Use separate End steps or an explicit Join where paths converge.
Start for a test record and answer through its question Task. Verify that only the selected outcome executes. Use a separate test run with a short timeout to check expiry. Keep the intended production timeout in the final publication; changing it later does not shorten an already waiting run.
Create a scheduled reminderโ
Recurring โ Create Task โ End
Configure weekdays at 09:00 in Europe/Vienna. Create Review today's open requests without linking a triggering record. This creates a reminder; it does not search for requests or generate one Task per request.
Check upcoming dates and offsets, publish and inspect the next eligible run. Pause after testing if needed. A previous open run can skip the next occurrence; see Schedules.
Classify a request, then assign concrete workโ
Manual record โ Agent โ If/Else โ Create Task โ End
Use a request with a readable text description. Create an Agent with an explicit description input, clear classification instructions, and two options: Urgent and Routine. No tools are needed. Publish the Agent, select it in the workflow and map the request description.
Compare output.option_id with the Urgent option's UUID. On true, create Review urgent request; on false, create Review routine request. Connect both paths to completion, using a Join if they share a following step.
Run two representative test records. Inspect the Agent's accepted option, usage and resulting Task. Preview cannot predict the model's choice. Adjust instructions or budgets through new published versions if the observed behavior needs improvement.