Connect Cord to any ERP or CRM. No waiting for a connector.

We don't maintain proprietary connectors for every system (SAP, Oracle, Salesforce…). Instead, Cord emits signed webhooks on every event of your sales cycle — point them at Zapier, Make, n8n, or your own backend and react in real time. Everything you see in the app is also available via REST API.

Start for free View plans

On every plan · webhooks capped by plan (Free 1 → Developer 100) · native Slack · free test keys for the API

POST tu-erp.com/webhooks/cord 200 OK

X-Cord-Event: quote.paid
X-Cord-Signature: sha256=4f1ad8c…
Content-Type: application/json

{
  "event": "quote.paid",
  "created_at": "2026-06-26T12:41Z",
  "data": {
    "folio": "COT-0149",
    "status": "paid",
    "total": 196469.2,
    "cliente": "El Zarco Distribution"
  }
}

delivered · auto-retry on failureHMAC-SHA256

OUTBOUND WEBHOOKS

Your system reacts to every sales event.

Register a URL under Settings › Developers › Webhooks and pick the events you care about. When a quote is sent, viewed, approved, rejected, paid, or invoiced, Cord POSTs the JSON payload. Each delivery is signed with HMAC-SHA256 in the X-Cord-Signature header so you can verify it came from Cord. It's best-effort with one retry, and every attempt is logged so you can replay it.

Header X-Cord-Signature: sha256=<hmac of the raw body> + X-Cord-Event
Payload with id, folio, status, total, client and public link
Delivery log with status, latency and a replay button in Settings

POST tu-erp.com/webhooks/cord 200 OK

X-Cord-Event: quote.paid

X-Cord-Signature: sha256=4f1ad8c…

{
  "event": "quote.paid",
  "data": {
    "folio": "COT-0149",
    "total": 196469.2,
    "cliente": "El Zarco"
  }
}

HMAC-SHA256 del cuerpo crudoreintento auto

NO PROPRIETARY CONNECTORS

Zapier, Make, n8n, or your backend.

Instead of locking you into a "native" connector per vendor, you point the webhook at a no-code platform (Zapier, Make, n8n) and from there reach thousands of apps —including SAP, Oracle, Salesforce, HubSpot or Notion— without us writing code for you. Want full control? Call the REST API directly. And if your team lives in Slack, that one is a native integration: alerts for every event arrive on their own.

Connect to 5,000+ apps via Zapier / Make / n8n with one webhook
Or use the REST API: create quotes, clients and products from your code
Native Slack: automatic notification on every quote event

Destinos del webhook 1 → ∞ apps

Zapier6,000+ apps sin código

Activo

Makeescenarios visuales

Activo

n8nself-hosted

Listo

Slackintegración nativa

Nativo

Tu backend / ERPendpoint HTTP propio

Directo

Sin esperar un conector propietario6 eventos

RELIABILITY

Deliveries you can trust

Every delivery, signed and verifiable

Every webhook goes out signed with HMAC-SHA256 in the X-Cord-Signature header — you compute the hash of the raw body with your secret and confirm it came from Cord, not someone else.

Automatic retry if the first delivery fails
Delivery log with status, latency, and manual resend

Zapier, Make, n8n, or your own backend

One webhook reaches thousands of apps without Cord maintaining a proprietary connector for each one.

Native Slack: automatic alerts per event

Unlike Zapier or Make, Slack needs no middleman: the notification lands straight in your channel.

From 1 endpoint (Free) to 100 (Developer)

The limit grows with your plan; overages are measured by API usage, not by the number of registered endpoints.

Secret shown once, never in plaintext

Copy it when you create it — after that only its fingerprint remains to sign with, no way to see it in full again.

FREQUENTLY ASKED QUESTIONS

What developers ask about Integrations & webhooks.

Does Cord have a native connector for SAP, Salesforce, or Oracle?

We don't maintain proprietary connectors per system. Instead, Cord emits signed webhooks (HMAC-SHA256) on every sales-cycle event that you point at Zapier, Make, n8n, or your own backend to connect with SAP, Salesforce, or any other system.

How many webhook endpoints can I configure?

It depends on your plan: from 1 endpoint on the Free plan up to 100 on the Developer plan. Overages are metered by API consumption, not by number of webhooks.

How do I verify a webhook really came from Cord?

Every delivery includes the X-Cord-Signature header with an HMAC-SHA256 of the raw body, signed with the secret Cord gave you when you created the endpoint — you validate it before processing the event.

REST API REST API Cord stops being just a screen for humans and becomes a system your other systems can talk to.