This guide provides a high-level overview of how to integrate Crono with n8n, using the Crono External API. n8n supports HTTP requests, which makes it possible to send data to Crono, create records, enrich information, and automate workflows without writing code.
This article explains the general logic of the integration. More detailed configuration guides and endpoint-specific examples are available in separate articles.
With n8n, you can automate any workflow that requires sending information to Crono. Common use cases include:
Creating Accounts or Contacts from external data sources
Syncing leads from spreadsheets, forms, CRMs, or webhooks
Adding items to Lists automatically
Triggering enrichment on new leads
Keeping Crono up to date with data from other tools
Building multi-step automations combining Crono with other platforms
If a workflow can produce data, n8n can send it to Crono.
Crono does not require a dedicated n8n integration.
Instead, you use n8n’s HTTP Request node to call Crono’s API endpoints.
Each request consists of:
The endpoint URL
A HTTP method (GET, POST, PUT, PATCH, DELETE)
Your API authentication headers
A JSON body (for POST, PUT, PATCH requests)
This approach makes the integration flexible and compatible with all current and future Crono API endpoints.
Before connecting n8n to Crono, ensure:
Your workspace is on the Ultra plan
Your role is Manager
You have generated your Public API Key and Private API Key
You can access the full API reference at: https://ext.crono.one/docs/
If any of these conditions are not met, you will not be able to authenticate requests.
All Crono automations in n8n use the HTTP Request node.
This node allows you to:
Set the request method
Add your authentication headers
Insert JSON bodies
Read the API response back into your workflow
In n8n create the HTTP request node following the steps below:
Inside a workflow add a node by press it plus button at the top right corner
Search for the HTTP Request node
Select the HTTP Request node
Every Crono integration starts by inserting this node and configuring it with the endpoint you want to call.
To authenticate with Crono inside n8n, you must add two headers:
X-Api-Key: your Public API Key
X-Api-Secret: your Private API Key
Both headers are required for every request. Here you can learn more on how to generate API keys in Crono.
One you have generated the keys, in order to add them inside the HTTP Request node, follow steps below:
Set Authentification as none
Turn on Send Headers
Then add both keys inside the header parameters
The endpoint you use depends on the type of data you want to send. Examples:
Create Account:/Accounts
Create Contact:/Contacts
Add items to a List:/Lists/{listId}/Items
Trigger Enrichment:/Enrich
Update a record:/Accounts/{id} or /Contacts/{id}
Use the base URL:
https://ext.crono.one/api/v1Full endpoint documentation is available here.
Most Crono API endpoints require a JSON body.
In n8n:
Enable Send Body
Set Body Content Type to Raw
Set Content Type to application/json
Insert your JSON payload
Dynamic data from previous nodes can be inserted using n8n expressions.
A dedicated article covers this in detail.
The HTTP Request node returns the API response as JSON, which can be passed to:
Additional n8n nodes
Decision logic
Updates into other tools
Notifications
Logging systems
This makes it easy to build multi-step workflows.
Integrating Crono with n8n is straightforward:
Use the HTTP Request node
Add your Crono API keys as headers
Choose the correct API endpoint
Send a JSON body where required
Use the response to continue your automation
This structure works for all Crono API endpoints and enables powerful automation and integration workflows.