CRM
Connect Pipedrive
Your application calls one EchoRelay URL. When Pipedrive changes its API, you update the mapping, not your application.
How Pipedrive signs requests
An API token in the x-api-token header. The token belongs to one user in one company.
Can you connect it today?
Yes. Add an API-key-in-a-header credential with the header name x-api-token.
A sample mapping
Your application sends the first request below. The mapping turns it into the body of POST /api/v2/deals, shown second.
Your request
{
"name": "Acme renewal",
"amount": 12000,
"currency": "EUR"
}
What Pipedrive receives
{
"title": "Acme renewal",
"value": 12000,
"currency": "EUR"
}
The mapping
{
"$schema": "https://schemas.echorelay.dev/transform/mapping/v1.json",
"root": {
"type": "object",
"id": "root",
"properties": {
"title": {
"type": "field",
"id": "title",
"path": "name"
},
"value": {
"type": "field",
"id": "value",
"path": "amount"
},
"currency": {
"type": "field",
"id": "currency",
"path": "currency"
}
}
}
}
The grammar, the answer mapping and the dry run are in the mapping docs.
What you bring
This is not a ready-made connector. You bring a sample request or Pipedrive’s OpenAPI document, you or your agent write the mapping, and we run the integration you define.
Pipedrive facts on this page were read 2026-10-29 from Pipedrive API authentication, Pipedrive API reference: deals. Another service? Check it here.
Connect everything. Deploy nothing.
No credit card required.