Flow Trigger

Trigger workflow on Flow project or task events

Overview

Trigger that listens for webhook events from Flow (getflow.com), a project management and task tracking application. Fires when changes occur on watched projects (lists) or tasks. The Flow API sends POST requests to the webhook URL whenever a subscribed resource changes. Supports monitoring specific project IDs or task IDs.

Category: Productivity
Tool Name: flow_trigger
Version: 1

Appearance: Icon: lucide-Workflow | Color: #00b0ff

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Flow API credentials. See the Credentials Guide for setup instructions.

Resources

Resource	Value
Project	list
Task	task

Select the resource type that triggers the webhook. It decides which ID parameter below applies.

Parameters

Parameter	Type	Required	Default	Description
Project ID	string	Yes	—	Project IDs (also known as “Lists” in the Flow API) separated by commas. A webhook is registered for each ID. (shown when Resource is list)
Task ID	string	Yes	—	Task IDs separated by commas. A webhook is registered for each ID. (shown when Resource is task)

Output Data

Flow may send a single object or an array of them. One output item is produced per payload object. The payload is copied onto the item unchanged, and three fields are added:

• _trigger — always flow_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the payload’s type, falling back to event, then to resource.changed

The Flow payload itself carries:

• resource_type — list for a project, task for a task
• resource_id — the watched resource the event belongs to
• id, name — the changed record
• workspace_id — the Flow workspace
• completed — whether the record is complete
• created_at, updated_at — record timestamps

Reference the payload downstream by expression, e.g. {{ $json.name }} or {{ $json.resource_id }}.

Usage Examples

• Start a workflow when a Flow task is updated
• Trigger automation when a Flow project changes
• Listen for task completion events in Flow
• Monitor Flow project activity via webhooks

Example Configuration

Monitor events for specific Flow projects:

{
  "id": "flow-trigger-1",
  "type": "flow_trigger",
  "typeVersion": 1,
  "position": [250, 300],
  "parameters": {
    "resource": "list",
    "listIds": "12345,67890,11111"
  }
}

Monitor events for specific Flow tasks:

{
  "id": "flow-trigger-2",
  "type": "flow_trigger",
  "typeVersion": 1,
  "position": [250, 300],
  "parameters": {
    "resource": "task",
    "taskIds": "22222,33333"
  }
}

Monitor a single project:

{
  "id": "flow-trigger-3",
  "type": "flow_trigger",
  "typeVersion": 1,
  "position": [250, 300],
  "parameters": {
    "resource": "list",
    "listIds": "98765"
  }
}

Trigger a workflow when any of several projects are updated:

{
  "id": "multi-project-trigger",
  "type": "flow_trigger",
  "typeVersion": 1,
  "position": [100, 200],
  "parameters": {
    "resource": "list",
    "listIds": "10001,10002,10003"
  }
}

Trigger a workflow when specific high-priority tasks change:

{
  "id": "task-specific-trigger",
  "type": "flow_trigger",
  "typeVersion": 1,
  "position": [100, 200],
  "parameters": {
    "resource": "task",
    "taskIds": "44444,55555"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Configure which Flow resource type (Project or Task) to monitor and provide the comma-separated IDs to watch. When those resources change in Flow, the webhook fires and starts this workflow.

Important Notes

• The resource parameter determines which ID parameter is available and required
• A webhook is registered for each individual ID provided
• The trigger will activate for any events occurring on the specified resources
• Ensure you have proper permissions for the Flow projects/tasks you want to monitor