Skip to main content
Creating your first workflow takes less than five minutes. You’ll open the Workflow Builder, attach a trigger to an event, wire up an action, validate everything with the built-in simulator, and flip the workflow live — all without leaving your browser.
1
Open the Workflow Builder
2
  • In the left navigation, click Automation.
  • Select the Workflows tab.
  • Click + New Workflow in the top-right corner.
    • 3
    A blank canvas appears with an empty trigger slot at the top. Give your workflow a name — for example, Notify team on task completion — by clicking the default title and typing a replacement.
    4
    Add a trigger
    5
    The trigger defines what starts your workflow. For this walkthrough, you’ll fire the workflow whenever a task is marked complete.
    6
  • Click the + Add Trigger slot on the canvas.
  • In the trigger panel on the right, choose Event-based.
  • Search for and select Task Completed.
  • Leave the filters empty for now so the trigger fires on every completed task.
  • Click Save Trigger.
    • 7
    The canvas now shows a Task Completed node at the top of the workflow graph. Every time a task is completed in your workspace, fsckmsft will pass the following payload to the next step:
    8
    {
  "event": "task.completed",
  "occurred_at": "2024-11-14T09:32:00Z",
  "workspace_id": "ws_01abc",
  "data": {
    "task_id": "t_abc123",
    "task_name": "Review Q4 budget",
    "completed_by": {
      "user_id": "u_xyz789",
      "name": "Alex Kim",
      "email": "alex@example.com"
    },
    "project_id": "proj_456",
    "priority": "high",
    "due_date": "2024-11-14"
  }
}
    9
    Add an action
    10
    Actions are the work your workflow performs. Here you’ll send a Slack message to your team channel.
    11
  • Click the + button beneath the trigger node.
  • Select Action from the step type menu.
  • Choose Send Slack Message from the action library.
  • In the configuration panel:
    • Channel: #team-updates
    • Message: Use the template editor to compose a dynamic message, for example: 
      ✅ Task "{{data.task_name}}" was completed by {{data.completed_by.name}}.
  • Click Save Action.
    • 12
    Your canvas now shows two connected nodes: Task Completed → Send Slack Message.
    13
    Use the Insert Variable button (the { } icon) in any text field to browse all available trigger payload fields and insert them without typing the path manually.
    14
    Test the workflow
    15
    Before activating, verify that the workflow behaves as expected using the built-in run simulator.
    16
  • Click Test in the top toolbar.
  • In the Run Simulator panel, choose Use sample payload or paste a custom JSON payload that matches the trigger schema.
  • Click Run Test.
  • Inspect the step-by-step execution trace — each node shows its input, output, and duration.
  • Check your Slack channel to confirm the message arrived (the simulator sends real requests during a test run).
    • 17
    The run simulator lets you replay any previous live event as a test input. Click Load from history in the simulator panel and pick an event from the last 30 days to test against real data without waiting for a new event to fire.
    18
    Activate the workflow
    19
    Once the test passes, make the workflow live.
    20
  • Click Activate in the top-right corner of the editor.
  • Confirm in the dialog — the workflow status changes from Draft to Active.
    • 21
    The workflow now runs automatically every time a task is completed in your workspace. You can monitor execution history, pause, or edit the workflow at any time from the Workflows list.
    Activating a workflow does not retroactively process past events. Only events that occur after activation will trigger a run.

    ​
    What’s next

    Conditions & Branches

    Route workflow execution down different paths based on data conditions.

    Error Handling

    Control what happens when a step fails and how to recover gracefully.

    Retry Policies

    Configure automatic retries with fixed, linear, or exponential backoff.

    Idempotency

    Prevent duplicate workflow runs when the same event fires more than once.