Connect n8n

n8n connects to Cord in two ways. The Cord node is the short path; the HTTP Request node covers any endpoint the node does not have yet.

With the Cord node

1. In n8n, go to Settings › Community nodes and install n8n-nodes-cord. You need a self-hosted n8n and admin rights on it. On n8n Cloud it will show up in the nodes panel once n8n finishes verifying it.
2. Create a secret key in Cord: turn on Developer mode in Your account › Preferences and open the Workbench’s API keys tab, the Developers pill in the bottom-right corner. The Create API key button in Settings › Integrations › n8n takes you there. Use a key with write permission; keys that start with sk_test_ work against your test environment.
3. In n8n, create a Cord API credential and paste the key. The test button queries your account and tells you whether the key is test or live.
4. Add the Cord Trigger node, choose the events and activate the flow: n8n registers the webhook in Cord for you and deletes it when you deactivate the flow.
5. To act on Cord, add the Cord node: clients (create, update, get, search), quotes (create, get, search, send, mark as paid) and tasks.

The trigger verifies the X-Cord-Signature-V1 signature on every delivery, so a POST to the webhook URL that does not come from Cord is discarded.

With the HTTP Request node

1. In Cord, add your webhook in the Workbench’s Webhooks tab with the URL from n8n’s Webhook node.
2. To call the API, use the HTTP Request node against https://cordhq.app/api/v1/... with the Authorization: Bearer sk_... header.

Limits

Webhooks and API calls count against your plan limits, the same as with Zapier or Make. This month’s API usage is in the Workbench’s Overview and API keys tabs (calls with test keys and from the Workbench don’t count), and your endpoints against the plan limit, in the Webhooks tab.