Described in plain words. With AI generation configured, an instruction becomes a starting draft — a trigger, steps and timing you can see.
Logic made explicit. Conditions, branches, pauses and loops handle the different paths your work can take.
Test before it runs. The draft stays inactive while you refine it; test with data before publishing.
Runs you can inspect. Review run activity and open any step when something fails.
From instruction to workflow · real screens
AI drafts it. You make it yours.
The lead handoff on real screens: describe it, inspect the canvas, refine the steps — and keep control over when it goes live.
01
Describe the process
Give the routine a clear instruction.
Ask AI to prepare a new-enquiry workflow: the lead trigger, a review task, a one-day wait and the follow-up. Review the proposed steps before accepting the draft.
Actual AI request in the workflow builder · before generation
02
Inspect the canvas
See the handoff from beginning to end.
The accepted draft shows the lead trigger, review task, one-day wait and follow-up task together — the full sequence in one place while the workflow stays inactive.
Actual saved workflow from the accepted AI plan · inactive draft, not tested
03
Refine the step
Make each action specific enough to use.
Open the review-task step and refine its title, description and priority. Check the remaining settings before testing or activation — you choose when it runs.
Actual task-step editor · details refined during review · inactive, untested workflow
Beyond the canvas
Work moves forward. Context stays with it.
The lead handoff uses CRM, Tasks and Automation. Extend the flow with the modules your process touches — each one optional.
Actual project task with Nora assigned · configuration demo, not a completed autonomous run
When the routine needs a role.
A workflow runs a sequence; an AI teammate holds a role — with responsibilities, memory and reviewable activity inside boundaries you set.
With AI generation configured, create a starting workflow from an instruction. Review its trigger, conditions and actions, then test it on your data before publishing. The screenshots include actual workflow previews.
What can start a workflow?
Use scheduled triggers or events from connected modules: CRM records, Inbox conversations or Forms & Documents submissions. Conditions, branches, pauses and loops shape what happens next.
Does Automation include documents?
Document templates and e-signing belong to Forms & Documents. Connect it to Automation for paperwork steps, and CRM when templates need lead or deal fields. Signing includes signers, field placement, status and signed PDF downloads.
Can we start with Automation alone?
Automation works on the modules and data in your workspace. This example uses CRM and Tasks; a different process may need different modules. We will map the triggers and actions to the setup you need.
Start with one routine
Build the process your team can rely on.
The lead-and-task example combines CRM, Tasks and Automation. Extend it with the modules your process touches, such as Inbox or Forms & Documents.
Nextora
