Workflow Pointer
Continue execution in another workflow you select from the workspace.
The Workflow Pointer operation transfers the run into another target workflow. That workflow must start with a Workflow Trigger node. Only the target workflow picker is configurable in the form.
When to use
- Reuse shared sequences (onboarding, escalation, CRM side-effects).
- Keep parent graphs small while delegating to a published sub-workflow.
- Organize automations by folder while linking across them.
Configuration
| Field | What it does | When to use |
|---|---|---|
| Select Workflow To Run | Lists workspace workflows by name; sets workflowId, workflowName, workflowFolderId | Pick the callee workflow |
| Refresh | Reloads workflow list | New workflows not visible yet |
| Description | Canvas note | Document handoff contract |
If loading fails, the form shows Error fetching workflows.
Flow behavior
- Input: Standard incoming edge from the parent flow.
- Output: One outgoing edge in the source workflow (after handoff is initiated).
- Target: Execution continues in the selected workflow at its Workflow Trigger.
- Pairing is by workflow id—ensure the target workflow is published and contains Workflow Trigger as its entry.
Examples
Centralized “create task” workflow
- Build Tasks – create with Workflow Trigger → Task node.
- In any customer flow, add Workflow Pointer → select Tasks – create after collecting details.
Folder-based organization
- Pick a workflow from another folder via the same dropdown (folder id stored on the node for reference).