That security review checklist, the legal sign-off steps, the “did anyone loop in IT?” task: every library has a chunk of process that shows up in workflow after workflow, each copy drifting slightly from the original. Now you can keep those steps in one place and pull them into any workflow that needs them.
What changed
The workflow editor has a new Workflow option in the add-task menu. Pick a workflow from your library, hit Add tasks, and its published tasks land at the end of your current draft. Everything that makes those tasks useful comes along: AI task prompts, Code task scripts, conditional logic wired to the right fields, form fields, approvals, assignments, permissions, and due dates.
How to use it
- Open a workflow in the editor.
- Click the + button at the bottom of the task list.
- Select Workflow.
- Browse or search for the workflow you want to pull tasks from, then click Add tasks.
- Review the imported tasks in your draft. Publish when you’re satisfied.
Smart handling, no surprises
- No name conflicts: if a form field name already exists in the target workflow, the imported field gets the next available name and its merge tags update automatically.
- Draft-safe: imported tasks land in your unpublished draft. Publish when ready, or discard the draft to undo the change entirely.
- One-time copy: later edits to the source workflow do not flow into workflows that already imported its tasks.
Good to know
- Automations, webhooks, and schedules are not included. Anything that connects to an external service stays with the source workflow. Set those up again on the target workflow after importing.
- Masked Code task inputs: if you don’t have edit access to the source workflow, masked inputs (like API keys) arrive blank. Fill them in before you publish.
This feature is available now for everyone on all plans. For a full walkthrough, check the help article on importing tasks from a workflow (coming soon).
