AutoVerse Workflow ControllerInstall

Summary

Creates a new workflow on the connected n8n instance from a workflow JSON object via the n8n public API, optionally activating it immediately.

Inputs

• workflowObject (required) — The workflow definition as JSON (object or JSON string), sent unchanged as the body of POST /workflows. It must satisfy the n8n public API's workflow schema (e.g. name, nodes, connections, settings). Invalid JSON, or a value that is not an object, raises an error. Default is {}.
• activateAfterImport — If true, calls the activate endpoint on the newly created workflow after creation. Default false.

Output shape

One item per input item, shaped as { workflow: }. If activation was requested, this is the response from the activate call. Otherwise it is the creation response.

Requires an n8nApi credential (base URL plus API key or token). Transient API errors (408, 425, 429, 5xx) are retried up to 3 times. API failures throw a NodeApiError, unless Continue On Fail is enabled, in which case an item containing { error } is returned. If creation succeeds but activation fails, the workflow remains created and inactive. The imported workflow is also added to the node's recently-used list in static data. The operation runs once per input item, so multiple items create multiple workflows.

Examples

Example 1: Deploy a workflow template exported from another n8n instance

Resource: Workflow, Operation: Import Workflow. Workflow Object set to the exported JSON, e.g. via expression {{ $json.workflow }}. Activate After Import off.

Example 2: Create and immediately enable a generated workflow

Workflow Object set to an expression building the JSON from an earlier node. Activate After Import on.

Links

• n8n community nodes installation guide