n8n

Connect n8n with an API key and a webhook URL so an agent can start your workflow during a call.

What you will achieve

n8n will show Connected, and you will know how workflows are started.

The connection can list your workflows and their runs, and start a workflow through its Webhook trigger. n8n can then reach hundreds of other apps.

An n8n instance (cloud or self-hosted) with the public API enabled. The n8n API is not available on the free trial.
A workflow that starts with a Webhook node, if you want to start workflows.

n8n controls these screens. n8n's guide: API authentication.

In n8n choose Settings, n8n API, and Create an API key. Copy it.
For a workflow you want to start: open its Webhook node and copy the Production URL (it contains /webhook/). Do not use the Test URL (/webhook-test/): it only answers while the editor is open and listening, so calls to it fail at random.
If the Webhook node uses Header Auth, note the header name and value.

Integrations, Connect on n8n.
Enter Instance URL (for example https://acme.app.n8n.cloud) and API key.
Optionally enter Webhook URL, Webhook auth header and Webhook auth value.
Choose Check and connect.

Field	Meaning
Instance URL	Your n8n address. A pasted API path or a bare host is tolerated.
API key	Sent in the `X-N8N-API-KEY` header to `<instance>/api/v1`. Required.
Webhook URL	Optional. The workflow's Production URL.
Webhook auth header / value	Optional. For a Webhook node with Header Auth. The API key is never sent to the webhook.

Plain http addresses and private network addresses are refused.

On an agent's Tools tab, Add tool, Integration, n8n:

Action	What it does	Runs
Trigger workflow	Starts the workflow whose webhook URL you saved with the connection and hands it the caller's name, phone, email and details. The agent cannot choose another workflow or address.	In the background

The workflow receives them as fields on its Webhook node. Listing workflows and runs stays in the dashboard and is not offered to agents.

Test connection should answer "n8n is responding."

The card shows Connected.

The check fails with 401. The API key is wrong, or the public API is not enabled on your plan.
"Could not reach the service." Check the instance URL and that it is reachable from the internet.
A webhook call fails sometimes. You used the Test URL; switch to the Production URL and activate the workflow.

The API key and webhook value are stored encrypted. Revoke the key in n8n to cut access. Remove forgets them here.

Something here does not match what you see in the dashboard? Let us know.