n8n

Build your agents and jobs in Ordify — where it's fastest and easiest — then plug them into more complex automations in n8n. The Ordify node for n8n lets you call your Ordify agents and jobs from any n8n workflow, so you can keep the AI logic in Ordify and use n8n for the orchestration around it.

Trigger an Ordify chat from a webhook, run a multi-agent job when a new row appears in a spreadsheet, or pipe agent outputs into hundreds of other n8n integrations — all without writing code.

Why use Ordify with n8n

• No-code orchestration: Combine Ordify agents with n8n's 400+ integrations in visual workflows.
• Trigger from anywhere: Start an Ordify job from any event n8n can listen to — schedules, webhooks, app triggers, file changes.
• Self-hosted control: Run n8n on your own infrastructure and keep workflow data inside your environment.
• Production-ready actions: Chat with agents, list available crews (jobs), execute jobs, and poll for results — all as standard n8n nodes.

Available actions

The Ordify node exposes the following actions:

Action	Description
Chat	Send a message to Ordify and receive a response. Supports two modes: General Chat (the default Ordify chat) and Specific Agent Chat (a direct conversation with a chosen agent). Optional features include thinking mode, grounding, RAG, and additional context.
List Available Agents	Fetch all agents available in your workspace
List Available Crews	Fetch all crews (jobs) available in your workspace
Get Crew Schema	Retrieve the input schema for a specific crew
Execute Crew	Trigger a crew/job to run, either asynchronously (returns a job_id) or synchronously (waits for completion)
Get Job Status	Poll the status of a running job
Get Job Result	Retrieve the final output of a completed job

Prerequisites

• A Linux or macOS host with Docker installed (Docker 20.10+ recommended)
• Port 5678 available on the host
• An Ordify account with an API key (see API)
• Outbound network access to npmjs.org from inside the container (for installing community nodes — see the troubleshooting note on corporate proxies)
• Basic familiarity with the terminal

Installation

These instructions install n8n self-hosted via Docker and add the Ordify community node from npm.

Step 1: Prepare a clean n8n data directory

This avoids conflicts with previously installed community nodes.

warning

The first command deletes your existing n8n data directory. Skip it if you have an n8n instance you want to keep.

rm -rf ~/.n8n
mkdir -p ~/.n8n
chmod 700 ~/.n8n

Step 2: Run the n8n container

Start n8n using the official Docker image, mounting the data directory you just created.

For testing (foreground, removed on stop):

docker run -it --rm \
  --name n8n \
  -p 5678:5678 \
  -v ~/.n8n:/home/node/.n8n \
  docker.n8n.io/n8nio/n8n

For a permanent setup (detached, auto-restart):

docker run -d \
  --name n8n \
  --restart unless-stopped \
  -p 5678:5678 \
  -v ~/.n8n:/home/node/.n8n \
  docker.n8n.io/n8nio/n8n

Open http://localhost:5678 in your browser and complete the initial owner signup.

note

With --rm, the container is removed (not just stopped) when you press Ctrl+C — but your workflows and credentials persist because they're stored in the mounted ~/.n8n directory. The detached form (-d --restart unless-stopped) is recommended for any setup you plan to keep around.

Step 3: Install the Ordify community node

Open a second terminal while n8n is still running.

Make sure the community nodes folder exists:

docker exec -it n8n sh -lc "mkdir -p /home/node/.n8n/nodes"

Install the Ordify node from npm:

docker exec -it n8n sh -lc "cd /home/node/.n8n/nodes && npm install n8n-nodes-ordify"

Step 4: Restart n8n

n8n only loads community nodes at startup, so you need to restart the container after installing.

If you're using the foreground command from Step 2:

1. In the terminal running n8n, press Ctrl+C to stop the container
2. Re-run the same docker run command from Step 2

If you're using the detached command:

docker restart n8n

Your workflows and credentials are preserved in ~/.n8n either way.

Step 5: Verify the node appears

In the n8n UI:

1. Click Create new workflow
2. Click Add node
3. Search for Ordify

You should see the Ordify node with the actions listed above.

If the node doesn't appear:

• Hard refresh your browser (Ctrl+Shift+R or Cmd+Shift+R)
• Check that the install ran inside /home/node/.n8n/nodes
• Confirm the container was restarted after the install

Configuring credentials

Before you can use the node, create an Ordify API credential in n8n.

1. In n8n, navigate to Credentials → New
2. Search for and select Ordify API
3. Set the following fields:

Field	Value
Base URL	https://r.ordify.ai/
API Key	Your Ordify API key

1. Click Save

You can find your API key in the Ordify app under Settings → API. See API for details.

Building your first workflow

1. Create a new workflow in n8n
2. Add a Manual Trigger node
3. Add an Ordify node and connect it to the trigger
4. Choose the Chat action
5. Select your Ordify credential
6. Pick a chat mode:

• General Chat — talks to the default Ordify chat
• Specific Agent Chat — talks directly to a chosen agent (you'll need the agent ID, which you can get from the List Available Agents action)

7. Enter a message and click Test workflow

You should see the response in the node output panel. From here, you can chain Ordify into any other n8n node — Slack messages, Google Sheets, databases, custom code, and more.

Upgrading and uninstalling

Upgrade to the latest version:

docker exec -it n8n sh -lc "cd /home/node/.n8n/nodes && npm install n8n-nodes-ordify@latest"
docker restart n8n

Uninstall the node:

docker exec -it n8n sh -lc "cd /home/node/.n8n/nodes && npm uninstall n8n-nodes-ordify"
docker restart n8n

note

The Ordify node is currently available for self-hosted n8n only. Support for n8n Cloud is coming soon.

What's next

• API — generate the API key you'll use in the credential
• What is a job — understand the crews/jobs you'll execute from n8n
• Triggers — Ordify's native trigger system as an alternative to n8n