Integrations and automation

Four paths to make Cord work with the rest of your systems. Pick the simplest one that solves your case.

Which one to use

Path	What for	Who sets it up
Cord Workflows	React inside Cord: create a task, email the team, post to Slack, or add a note in HubSpot.	Anyone on the team, from the app.
HubSpot	Keep clients, contacts and Deals up to date without entering data twice.	Connected once in Settings.
Zapier and Make	Connect Cord with another tool you already use, without running a server.	Whoever builds the Zap or scenario.
API v1 + webhooks	Full control: your backend decides what to do with each event.	Your development team.

Cord Workflows

It lives in the app, not in the API. A workflow listens to a Cord event, evaluates conditions, can wait for days, and runs actions. Every run is recorded with its result.

Use it when the automation starts and ends inside Cord. If you need to touch another system, use one of the paths below.

HubSpot

Cord manages the sync: clients with Companies and Contacts both ways, and every quote creates and moves its Deal through the pipeline you choose. It needs no code and does not use your webhook allowance.

Zapier and Make

Both platforms talk to Cord’s public API and connect through OAuth 2.0: the person authorizes on a Cord screen and there are no keys to create or paste. Each authorization becomes a short-lived credential that Cord renews with a refresh token, and it shows up in the API keys tab of the Cord Workbench as an Authorized connection.

Events out: a webhook subscription created with that connection’s credential. They are created and deleted automatically when you turn the Zap or scenario on and off.
Actions into Cord: the /api/v1 endpoints with that same credential.

Cord registers OAuth clients on request; there is no self-service registration. Today there are registered clients for Zapier and Make, plus the Cord add-on for Gmail, which belongs to Cord itself. If you’re building an app other businesses will connect, follow OAuth for apps. For your own server, use a secret key.

n8n

The n8n-nodes-cord community node (on npm) uses a secret key in its Cord API credential: every n8n install has its own return address, so it does not connect through OAuth. Its trigger registers the webhook when the workflow is activated and verifies the X-Cord-Signature-V1 signature. Today it installs on self-hosted n8n; version 1.1.0 was published with provenance and submitted to n8n’s verification on September 21, 2026, and it will appear in n8n Cloud once n8n approves it.

Subscriptions created through the API have their own allowance of 100 per organization, separate from the endpoints your team configures. The details are in Webhooks.

If you prefer to build it by hand in Make, the support guide walks through the Webhooks and HTTP modules.

API v1 and webhooks

The full path: authenticate with a secret key, listen to the events you care about, and respond from your backend.

Authentication
Webhooks, with the event list, the X-Cord-Signature-V1 signature, and delivery history.
MCP server, when an AI assistant is the one consuming Cord.