Resources · n8n integration

Flow n8n integrationAutomate Flow with n8n.

Can a task list run itself while the team keeps working? That is what a Flow n8n integration buys: 4 operations on a single Task resource, plus a Flow Trigger that listens on a webhook, a URL Flow calls the moment something happens. Built for teams whose day already lives in tasks.

Try the Flow integration on n8n See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

Why build a Flow n8n integration?

A Flow n8n integration wires your Flow workspace into the rest of your tooling without anyone writing a service for it. The node covers 4 operations on 1 resource, Task: create one, update one, read one, read many. The Flow Trigger sits at the front of a workflow and fires it when Flow calls the webhook URL that n8n registered when you activated the workflow.

Start with intake, because that is where retyping happens. A form reply or a signed quote lands in n8n, the workflow calls task.create with the workspace and a title, and the task shows up in the right list with a due date already set. The person who asked for the work never opens Flow, and nobody copies a sentence twice.

Reporting is the second pattern. A Schedule node fires each morning, task.getAll reads the task list with Return All switched on, and the rows drop into Google Sheets where the weekly review already lives. The same batch can feed a short digest in Slack instead, so the standup starts with numbers rather than a scroll through boards.

Third, keeping two boards honest. The Flow Trigger receives an event for the tasks you registered, the workflow reads that task with task.get, and the change is mirrored into ClickUp. Teams that split delivery across two tools stop discovering the drift a week later.

Anything the catalog does not cover, you call yourself: the HTTP Request node reaches any Flow API endpoint and reuses the exact same credential, so there is no second token to manage. That fallback matters more than it sounds: it means a missing operation slows you down for an afternoon instead of sending you back to a developer.

Tasks are the whole surface of this node, which keeps the learning curve short. If you want to judge the platform before you build something that matters, the n8n review goes through it in detail, and the n8n training walks through building workflows end to end.

Connect

How do you connect Flow to n8n?

01
Generate the access token in Flow
You need a Flow account first. Inside it, generate an Access Token and note your numeric Organization ID, the two values the credential asks for. Flow documents both in its API Getting Started page, which is the only place worth trusting for the exact clicks. Keep the token somewhere safe while you finish the setup, because it is the whole authentication method here.
02
Save the credential in n8n
Open the Credentials menu in n8n and create a Flow credential, the stored authentication that nodes reuse. Paste the numeric Organization ID in one field and the Access Token in the other. You do this once per Flow account: every workflow you build afterwards picks the same credential from a dropdown, and rotating the token later means editing a single record.
03
Point the node at that credential
Drop a Flow node on the canvas, select the credential you just saved, and pick the Task resource with the Get many tasks operation. Run the node once with no filter: if tasks come back, the token and the organization match. The Flow Trigger uses that same credential, so a working node means the trigger is ready too.

Triggers

What starts a Flow workflow?

Flow Trigger is the node that starts a workflow when Flow calls n8n. Activate the workflow: n8n gives you the webhook URL to register in Flow, and every call becomes an execution.

What you see in n8n

Configuration notes

01Configure the Flow TriggerThe Flow Trigger is the node that opens a workflow instead of closing it. It works over a webhook, meaning n8n exposes a URL that Flow calls when something happens, so events land in a few seconds and nothing is polled on a timer. The webhook is registered when you activate the workflow.

The Flow Trigger is the node that opens a workflow instead of closing it. It works over a webhook, meaning n8n exposes a URL that Flow calls when something happens, so events land in a few seconds and nothing is polled on a timer. The webhook is registered when you activate the workflow.

Key parameters

Resource: chooses which Flow resource triggers the webhook, so one workflow listens to one kind of thing rather than everything at once.
Project ID: required, the list IDs, which Flow users know better as projects, separated by a comma when you want several of them.
Task ID: required, the task IDs to watch, also separated by a comma.

Use cases

a delivery team registers the project that carries client work, so any movement inside it reaches n8n while the rest of the workspace stays quiet.

02New Flow eventThis is the single event the trigger listens to. Flow sends it to the registered URL, and n8n turns it into one item that starts the run. Read what you need from it with an expression, the n8n syntax that reaches into the incoming item, written as {{ $json.field }} in any field of a later node.

This is the single event the trigger listens to. Flow sends it to the registered URL, and n8n turns it into one item that starts the run. Read what you need from it with an expression, the n8n syntax that reaches into the incoming item, written as {{ $json.field }} in any field of a later node.

When to use it

whenever the workflow has to react to Flow rather than to a clock. If your logic is really a daily or hourly sweep across many tasks, a Schedule node followed by Get many tasks costs less and reads better than a trigger you filter afterwards.

Use cases

an event on a watched task kicks off a run that reads the task, then writes a line into the client report without anyone chasing an update.

Actions

What can the Flow node do?

The Flow node exposes 4 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Create	Get	Get Many	Update
Task	✓	✓	✓	✓

Task

4 operations

Create a task

task.create

What you see in n8n

Notes & use cases

Creates a task in Flow from data already travelling through the workflow, with its title and its home workspace decided at creation time.

Key parameters

Workspace ID: required, the workspace the task is created under, often {{ $json.field }} from the node before.
Name: required, the title of the task.
Additional Fields: 14 optional fields, among them List ID to file the task in a list (leave it out and the task stays private), Due On for the due date, and Tags as tag names separated by a comma.

Use cases

a signed quote creates the kickoff task in the client list, tagged and dated, before the account manager has opened a tab.

Update a task

task.update

What you see in n8n

Notes & use cases

Rewrites an existing task in place. You say which task and which workspace, then send only the fields that change, leaving everything else untouched.

Key parameters

Workspace ID: required, the workspace the task belongs to.
Task ID: required, the identifier of the task to modify, typically {{ $json.field }} carried over from an earlier node.
Update Fields: 16 optional fields, including Completed to close the task, Owner ID to hand it to someone else, and Section ID to move it under another section.

Use cases

a deal marked won in the CRM closes the matching task and reassigns the follow-up in one run.

Get a task

task.get

What you see in n8n

Notes & use cases

Reads one task and hands it to the rest of the workflow, so the next nodes work on real values rather than on what someone assumed was there.

Key parameters

Task ID: required, the identifier of the task to read, usually {{ $json.field }} from the trigger or a lookup.
Filters: one field, Include, which pulls extra material along with the task: schedule, files, file_associations or parent.

Use cases

before a status email goes out, the workflow reads the task with its files included, so the client gets the attachment and not a promise of one.

Get many tasks

task.getAll

What you see in n8n

Notes & use cases

Reads a batch of tasks in one go, which is what reporting and cleanup passes need. Nothing is required, so it runs as is and you narrow it down afterwards.

Key parameters

Return All: switched on, n8n walks the pages of the Flow API and brings back every matching task; switched off, Limit caps how many come back.
Filters: 9 fields to cut the batch down, among them Workspace ID, Order to sort on due_on or created_at, Created After, and Deleted to include deleted tasks.

Use cases

a Monday run lists everything created since the last one and turns it into the report the team actually reads.

Need help

Need help automating Flow with n8n?

A person reads every message.

FAQ

Flow and n8n, the questions that come next

01Is the Flow n8n integration free?

Yes on the n8n side. The Flow node and the Flow Trigger ship with n8n, so there is nothing to install and nothing extra to pay: they behave the same on n8n Cloud, the hosted offer run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow built in one runs in the other without changes. What a Flow plan costs on Flow's side is a separate question, and it is not something this page can answer for you. The only thing you need before building is a Flow account able to issue an access token.

02What credentials does the Flow node need?

One API key credential, shared by both nodes. It asks for two values: your numeric Organization ID and an Access Token, both documented in Flow's API Getting Started page. You create that credential once in the n8n Credentials menu, and every Flow node or Flow Trigger you add afterwards picks it from a dropdown instead of asking again. That also means one place to update when you rotate the token. A field marked required in a node, such as Workspace ID or Task ID, stops the execution when it is empty, so fill those before running rather than debugging a silent branch later.

03What are the limits of the Flow node in n8n?

The node exposes 4 operations on 1 resource, Task, so everything you build with it revolves around creating, updating and reading tasks. Anything outside that catalog goes through the HTTP Request node, which calls any Flow API endpoint while reusing the same credential through predefined authentication, so you keep one token and one setup. On reads, watch Return All: switched on, n8n chains the pages of the API and brings back the whole set; switched off, Limit decides how many tasks come back, which is the usual reason a report looks suspiciously short.

04Does the Flow Trigger react in real time?

Yes. The Flow Trigger works over a webhook: n8n registers its URL with Flow when you activate the workflow, Flow calls that URL, and the event reaches the workflow within seconds. There is no polling interval to tune and no waiting for the next check. Two practical consequences: the workflow has to be active for the webhook to exist, and the trigger only watches what you registered through Project ID and Task ID, not the entire workspace. If you need a broad sweep rather than a reaction, pair a Schedule node with Get many tasks.

05n8n or Make for Flow?

It comes down to four criteria, and neither tool is wrong. Hosting: n8n runs on your own server or on n8n Cloud, Make is hosted only. Data control: self-hosting keeps task titles and client names inside your infrastructure, which matters in some industries and not at all in others. Cost model: Make bills per operation, so a workflow that reads every task each morning gets expensive as the board grows, while a self-hosted n8n bills you the server. Visual logic: both draw the flow on a canvas, and the habit you already have counts more than the pixels.

Generate the access token in Flow

Save the credential in n8n

Point the node at that credential

Configuration notes

Need help automating Flow with n8n?