Importing and Copying Workflows

QuickFlo’s workflow builder supports copying and pasting workflow definitions directly via the system clipboard. Share workflows as JSON, import pre-built templates, or duplicate steps across projects — all with Cmd+C / Cmd+V.

Pasting a Workflow

To import a workflow from JSON:

1. Copy a workflow JSON definition to your clipboard
2. Open the workflow builder
3. Press Cmd+V (Mac) or Ctrl+V (Windows/Linux)
4. The steps appear on the canvas at your cursor position

QuickFlo automatically handles ID collisions — if a pasted step has the same ID as an existing step, it gets renamed (e.g., my-step becomes my-step-1).

Tip

This works with full workflow definitions, individual steps, or arrays of steps. QuickFlo detects the format automatically.

Supported JSON Formats

Full Workflow Definition

The most complete format — includes steps, initial data, and workflow options:

{
  "name": "My Workflow",
  "steps": [
    {
      "stepId": "fetch-data",
      "stepType": "core.http",
      "input": {
        "url": "https://api.example.com/users",
        "method": "GET"
      }
    },
    {
      "stepId": "transform",
      "stepType": "core.map",
      "input": {
        "array": "{{ fetch-data.body.data }}",
        "mappings": [
          { "targetPath": "name", "value": "{{ $item.firstName }} {{ $item.lastName }}" },
          { "targetPath": "email", "value": "{{ $item.email }}" }
        ]
      }
    }
  ],
  "initial": {
    "apiKey": "your-key",
    "limit": 100
  }
}

When pasting a full definition, the initial data and workflow options are also imported.

Array of Steps

Paste multiple steps at once:

[
  {
    "stepId": "get-user",
    "stepType": "core.http",
    "input": {
      "url": "https://api.example.com/users/{{ initial.userId }}",
      "method": "GET"
    }
  },
  {
    "stepId": "send-email",
    "stepType": "core.send-email",
    "input": {
      "to": "{{ get-user.body.email }}",
      "subject": "Welcome!",
      "body": "Hi {{ get-user.body.name }}"
    }
  }
]

Single Step

Import a single step definition:

{
  "stepId": "check-status",
  "stepType": "core.http",
  "input": {
    "url": "https://api.example.com/status",
    "method": "GET"
  }
}

Form Definition

Paste a form trigger definition to recreate a form on a workflow that has a form trigger. The clipboard accepts the form’s schema (the field config) and meta (title, layout, branding) in a single JSON object:

{
  "schema": {
    "type": "object",
    "properties": {
      "first_name": { "type": "string", "x-quickforms-label": "First name" },
      "email": { "type": "string", "format": "email" },
      "use_case": { "type": "string", "x-quickforms-widget": "textarea" }
    },
    "required": ["email"]
  },
  "meta": {
    "title": "Contact Us",
    "submitButtonText": "Send",
    "layout": "standard"
  }
}

When you paste this into the form builder, the existing fields are replaced with the imported schema, and the metadata (title, layout, etc.) is applied. Useful for porting a finished form between workflows or sharing a form template with a teammate.

Step Definition Fields

Each step in the JSON supports these fields:

Field	Required	Description
stepId	Yes	Unique identifier for the step
stepType	Yes	The step type (e.g., core.http, core.if, core.for-each)
input	No	Configuration object — fields depend on the step type
continueOnError	No	If true, the workflow continues even if this step fails (catches both execution and operational errors)
skipCondition	No	A JSONLogic expression that, when truthy, skips the step at runtime — e.g. { "==": ["{{ $vars.env }}", "staging"] }
retryPolicy	No	Retry config: { maxRetries (1–10), delayMs, backoffMultiplier } for exponential backoff on transient failures

Container Steps

Steps with nested children (like for-each, if, switch) include their children in the input:

{
  "stepId": "process-items",
  "stepType": "core.for-each",
  "input": {
    "array": "{{ fetch-data.body.items }}",
    "steps": [
      {
        "stepId": "enrich",
        "stepType": "core.http",
        "input": { "url": "https://api.example.com/enrich/{{ $item.id }}" }
      }
    ]
  }
}

Copying Steps

Keyboard Shortcut

1. Select one or more steps on the canvas
2. Press Cmd+C (Mac) or Ctrl+C (Windows/Linux)
3. The step definition JSON is copied to your system clipboard

You can paste it into another workflow, another browser tab, or share it with a teammate.

Context Menu

Right-click any step and select Copy Step to copy its definition to the clipboard.

Copy Workflow Definition

From the Workflows page, right-click any workflow card (or open its menu) and select Copy Workflow Definition.

This copies the complete workflow definition — including all steps and the configured initial data. It’s more convenient than selecting all steps on the canvas with Cmd+C, which only copies the step definitions without initial data.

Keyboard Shortcuts

Action	Mac	Windows/Linux
Copy step(s)	Cmd+C	Ctrl+C
Cut step(s)	Cmd+X	Ctrl+X
Paste step(s)	Cmd+V	Ctrl+V
Select all	Cmd+A	Ctrl+A
Execute workflow	Cmd+Enter	Ctrl+Enter
Toggle AI Builder	Cmd+I	Ctrl+I
Toggle Results Panel	Cmd+E	Ctrl+E

Note

Only valid step types can be imported. If the JSON contains a step type that doesn’t exist in your step library, you’ll see a notification listing the unrecognized types.