Calimatic Connect|Documentation
PricingSign In

CRM Push

CRM Push sends your data to your CRM automatically. When data arrives from a connected source, it is delivered to Salesforce, HubSpot, or any other connected CRM — no manual work required.

CRM Push is one type of destination in Calimatic Connect. For routing data to other tools (Slack, email, webhooks), use Flows.

Where Can Leads Be Sent?

CRM Systems (API-Based)

Leads are sent directly to your CRM via its API. Calimatic Connect handles authentication and formatting for you.

  • Salesforce — Creates Lead objects automatically
  • HubSpot — Creates contacts in your HubSpot CRM
  • Custom CRM — Sends data to any REST API endpoint you configure

Need to send leads to other tools? Use Flows to set up automated actions between any connected providers.

What Happens When a Lead Arrives

When a new lead comes in, Calimatic Connect automatically:

  1. Finds all your connected CRM destinations
  2. Applies your field mapping rules to format the data correctly
  3. Sends the lead to each destination
  4. Reports success or failure for each one

This happens in the background, so it does not slow down lead processing. If you have set up Flows, they can also trigger CRM pushes with per-flow control over which leads go where.

Automatic Retry

If a destination is temporarily unavailable, Calimatic Connect retries automatically:

SettingValue
Retry attemptsUp to 3
Wait between retriesStarts at 1 second, up to 15 seconds
Retries on server errorsYes
Retries on rate limitsYes (429 responses)
Retries on other client errorsNo

If retries are exhausted, the system's scheduled job will automatically try again later. You can also trigger a manual retry from the admin panel.

For Developers: API Endpoints

Push a Single Lead

POST /crm/push/:leadId
# Pushes the lead to all connected destinations for the account

Batch Push

Push all pending (unsynced) leads for an account to all connected destinations:

POST /crm/push-batch/:accountId
# Pushes all pending leads for this account

Test Connection

Before relying on a destination, verify that the connection is working:

POST /crm/:accountId/test
# Tests all destination connections for the account
# Response
{
"results": [
{ "provider": "custom_crm", "success": true, "message": "OK" },
{ "provider": "hubspot", "success": true, "message": "OK" }
]
}

Configuring Destinations

Set up your destinations by connecting a provider. Here are examples for common destination types:

Custom CRM (API-Based)

For developers: Connect a custom CRM endpoint via API:

POST /connect/v1/providers/custom_crm/connect
{
"credentials": { "apiKey": "your-crm-api-key" },
"config": {
"apiUrl": "https://your-crm.com/api",
"leadEndpoint": "/v1/leads"
}
}

Multiple Destinations

You can connect multiple destinations per account. Leads are sent to all of them simultaneously. A push is considered successful if at least one destination receives the data successfully.