docs
EnglishChatigram website ↗Open Chatigram
Build workflows

Copy and paste workflows

Reuse a complete workflow or a single node with Chatigram’s portable JSON formats, and map destination resources before activation.

Plan availability #

Feature Free Starter Pro Enterprise
Active workflows 3 10 45 Unlimited

Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.

Copy a complete workflow #

If the source is already in your organization, you can create a new workflow through Copy Existing Workflow without transferring JSON. Choose the existing workflow or project and review the resulting copy. See workflow starting points for how that differs from Blank Workflow, Official Templates, and Paste/Import Workflow.

Use the workflow’s copy action to copy its portable JSON. This describes its trigger, nodes, Properties, and connections between steps. Copying a workflow is different from enabling it or running it.

Choose a recipe in this documentation to get a complete example with a Copy workflow JSON button and a download link.

Import a workflow #

  1. Open Workflows and start creating a workflow.
  2. Choose Paste/Import Workflow.
  3. Paste the JSON into Workflow JSON, or use Paste from Clipboard.
  4. Validate and confirm the pasted definition, then continue with Next.
  5. Give the new workflow a clear name.
  6. Review the preview, import help, Properties, and destination requirements.
  7. Finish creating it, open the editor, and inspect the nodes before activation.

If the browser cannot read the clipboard, paste manually with Ctrl V, ⌘ V, or the context menu. Copy the JSON itself, without the surrounding Markdown code fences.

Copy and paste one node #

Use Copy node on the node you want to reuse. At a free branch, open the node selector’s Paste Node view, paste its Node JSON, and choose Add Node.

A pasted node is a new instance. Recheck references to other nodes, selected accounts, and resource selections. Trigger nodes are not copied as ordinary nodes; use a whole-workflow copy to preserve the starting event.

Here is a complete Send Text Message node example:

Node JSON
{
  "format": "chatigram-node",
  "version": 1,
  "nodeType": "SEND_TEXT_MESSAGE",
  "name": "welcome",
  "data": {
    "message": [
      { "$tag": "Constant", "value": "Hello! How can we help today?" }
    ]
  }
}

Paste it into a conversation workflow. A Manual workflow has no customer conversation for this node to reply to.

Review destination-specific resources #

Resource What to check after import
App Connection Select an account available in the destination organization
Database or table Select the local resource and review column mappings and filters
Conversation status Choose the intended local status
Uploaded file or image Ensure the destination organization can use it
Custom Node Type Resolve or replace the definition and review inputs and outputs
Workflow Properties Supply the settings the new workflow needs
Line assignment Include the new workflow in the intended Line selection

Imported definitions do not transfer ownership or access permissions for resources.

Understand the JSON formats #

  • chatigram-workflow, version 1: a whole workflow definition for the workflow creation/import flow.
  • chatigram-node, version 1: one node’s configuration for Paste Node.
  • chatigram-node-type, version 1: a reusable Custom Node Type definition for its dedicated import flow.

These are different formats with different destinations. A workflow’s nodes array is not a standalone node import, and a reusable node definition is not an ordinary workflow.

Fix an import error #

Use the full JSON object and the correct import screen. Check for a missing node type, an unavailable resource, a broken variable reference, or an invalid graph. If importing an old example, compare it with a fresh export from the current application.

After importing, test the new workflow with controlled inputs. Imported instructions and data never grant permission to use an account or resource you cannot access.

Keep building.Need help with this? Explore troubleshooting ↗

Find an answer. Try “welcome workflow”, “database”, or “Telegram”.