Connect Cord with Make
The Cord app for Make lets you start a scenario when a quote moves forward and create or update Cord data from any other app.
Connect it
- In Cord open Settings › Integrations › Make and click Open Cord on Make. Click Install, pick your Make organization and confirm. Make only lets Admins, Owners or App Developers of that organization install apps; if you are not one, ask someone who is.
- In Make, inside a scenario, add a Cord module and click Create a connection › Save.
- On the Cord screen pick the workspace and click Authorize. There are no keys to create or paste.
You need access to Settings in that workspace to authorize. To cut the access, open the API keys tab of the Developers Workbench (the View authorized connections link in Settings › Integrations › Make takes you there) and revoke Make’s connection, which shows as Authorized connection.
What you can do
- Instant trigger: Watch Events, with the Cord events you choose.
- Actions: create, update and get clients; create, get and send quotes; mark them paid and create tasks.
- Searches: clients and quotes.
- Make an API Call: any other operation in the Cord API.
Without installing the app
You can also connect Cord with Make using two modules Make already includes: Webhooks to receive Cord events and HTTP to call the Cord API.
Receive Cord events
- In your Make scenario, add the Webhooks › Custom webhook module, create a webhook, and copy the URL Make gives you.
- In Cord, turn on Developer mode in Your account › Preferences and open the Webhooks tab of the Workbench, the Developers pill in the bottom-right corner.
- Click Add endpoint, choose the events you care about (for example
quote.approved), paste the Make URL, and click Create endpoint. - In Make, click Redetermine data structure, then use the endpoint’s Test button in Cord. Make learns the shape of the event, and you can map fields like
data.folio,data.total, ordata.cliente.
Every event arrives with id, event, created_at, and data. Use the id so you don’t process the same event twice if Cord retries the delivery.
Make does not verify Cord’s signature for you. Treat the webhook URL as a secret: don’t share it, and if you think it leaked, delete the endpoint in Cord and create a new one.
Each endpoint counts toward your plan’s webhook limit.
Create or update data in Cord
- In Cord, create a secret key with write permission from the API keys tab of the Developers Workbench.
- In Make, add the HTTP › Make a request module.
- Set it up like this:
- URL: the endpoint you need, for example
https://cordhq.app/api/v1/clientes. - Method:
POSTto create,PATCHto update. - Headers:
Authorizationwith the valueBearer sk_live_...andContent-Typewithapplication/json. - Body type:
Raw, JSON content, with the resource fields.
- URL: the endpoint you need, for example
- If the scenario can retry, add an
Idempotency-Keyheader with a fixed value per operation, for example theidof the event that started it. That way a retry doesn’t create the record twice.
What you can do from Make:
- Create a client with
POST /api/v1/clientesor update it withPATCH /api/v1/clientes/{id}. - Find a client by email with
GET /api/v1/clientes?email=.... - Create a quote with
POST /api/v1/cotizaciones. - Send it or mark it paid with
POST /api/v1/cotizaciones/{id}andaction. - Create a task with
POST /api/v1/tareas.
The fields for each endpoint are in the developer documentation.