Workflow Editor

The Workflow Editor is the visual interface where you build, configure, and test your automation workflows. It uses a node-based canvas where you connect triggers to actions in a visual flowchart, making it easy to understand and modify complex workflows without writing code.

Editor Layout

The workflow editor is divided into three main areas:

Canvas

The main area where your workflow is displayed as a visual flowchart. Each step (trigger, action, condition, delay) is represented as a node on the canvas. Nodes are connected by lines showing the execution flow.

You can:

• Pan — Click and drag the canvas background to move around
• Zoom — Scroll to zoom in/out
• Select nodes — Click a node to select and configure it
• Move nodes — Drag nodes to rearrange the layout
• Connect nodes — Drag from one node's output to another node's input to create a connection

Node Configuration Panel

When you select a node, a configuration panel appears on the right side. This panel shows all settings for the selected node:

• Trigger nodes — Configure which event fires the trigger, optional filters (e.g., only for a specific board), and view the data schema the trigger provides
• Action nodes — Configure the action's parameters, map data from the trigger or previous actions using variable selectors, and set optional conditions
• Condition nodes — Define the condition expression, configure the true/false branches
• Delay nodes — Set the wait duration

Node Palette

A panel showing all available node types that you can add to your workflow. Nodes are categorized:

• Triggers — Card, content, board, and workspace event triggers
• Logic — Condition, delay, data transform
• Communication — Email, announcement, webhook
• Discord — All 17 Discord actions
• Slack — Channel message, DM

Drag a node from the palette onto the canvas to add it to your workflow.

Building a Workflow

Step 1: Add a Trigger

Every workflow starts with exactly one trigger. Drag a trigger node from the palette or click "Select Trigger" on the starting node. Configure which event should start this workflow.

Optional trigger filters: Narrow down when the trigger fires. For example, the "Card Moved" trigger can be filtered to only fire when a card moves to a specific list, or on a specific board.

Step 2: Add Actions

Drag action nodes from the palette and connect them to the trigger (or to previous actions). Each action executes in the order it's connected.

Mapping data: When configuring an action's parameters, you'll see a variable picker that lets you reference data from:

• The trigger event (e.g., the card title, the user who triggered it, the board name)
• Previous action outputs (e.g., the result of a prior action)

The variable picker shows the exact data available, so you can simply browse and select the values you need.

Step 3: Add Logic (Optional)

For workflows that need branching:

• Conditions — Add a condition node between actions to branch based on data values. The condition has two outputs: true and false, each leading to different action chains.
• Delays — Add delay nodes where you need the workflow to pause before continuing.
• Data Transforms — Add transform nodes when you need to reshape data between steps.

Step 4: Test

Before activating your workflow, test it with sample data:

1. Click the Test button
2. The editor generates sample trigger data based on your trigger type
3. The workflow executes with the sample data
4. Each node shows its result — you can verify that data is flowing correctly and actions are configured properly

Step 5: Activate

Once you're satisfied with the test results, click Activate to enable the workflow. From this point, the workflow will fire automatically whenever its trigger event occurs.

Editing Existing Workflows

Navigate to Automations in the sidebar and click any workflow to open it in the editor. All your existing nodes, connections, and configurations are preserved. Make changes and save — the updated workflow takes effect immediately.

Workflow Settings

Each workflow has settings accessible from the editor:

• Name — A descriptive name for the workflow (shown in the automations list)
• Description — Optional notes about what the workflow does and why
• Folder — Which folder the workflow is organized in
• Enabled/Disabled — Toggle the workflow on or off

Tips for Complex Workflows

• Name your actions — Give each action node a descriptive name so the workflow is self-documenting
• Use conditions sparingly — Simple linear workflows are easier to debug than heavily branched ones
• Check run history — After activating, monitor the first few executions in Run History to verify everything works as expected
• Start simple — Build a minimal workflow first, test it, then add complexity incrementally