Solution
Route new leads to your CRM, Slack, and sales team at once
A form fill or ad-platform lead comes in once. API Rabbits fans it out to your CRM, notifies sales in Slack, and logs it for reporting — all from a single POST.
The scenario
Your landing page, ad platform, or lead-gen tool submits a lead. Today that might go straight to one CRM. With a rabbit in front of it, the same event can create the CRM record, ping the right Slack channel, and get logged for attribution reporting — without your form code knowing any of those destinations exist.
Example routing rule
Route to the enterprise Slack channel and Salesforce only when "company_size" is above 200; everything else goes to the SMB pipeline in HubSpot.
POST /v1/p/leads-example
{
"email": "sam@acme.com",
"name": "Sam Rivera",
"company": "Acme Co",
"source": "google-ads",
"campaign": "q3-demo-signups"
}Fans out to:
- HubSpot / Salesforce — Create or update the contact record.
- Slack — Notify the sales channel with a formatted message.
- Activity log — Keep a queryable record for attribution reporting.
One field, multiple systems
Sales, marketing, and reporting each want the same lead in a different tool. A rabbit sends it to all of them from one submission, so no team is stuck waiting on another to forward data.
Conditional routing by lead quality
Use routing rules to send only qualified leads to your CRM and notify sales in real time, while lower-intent leads go straight to a nurture list.
Nothing gets lost
If your CRM's API has a bad minute, that delivery retries on its own schedule — it doesn't block the Slack notification or the log entry from going through.