Integration
Connect CallRail to HubSpot Enterprise
When something happens in CallRail, your agent does the next thing in HubSpot Enterprise. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CallRail and HubSpot Enterprise to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with CallRail and HubSpot Enterprise
Triggers and actions 6 triggers ยท 3 actions
Trigger
Form CapturedTriggers when a form is captured.
- Outbound Call Completed
Triggers after an outbound phone call has been completed and its recording and transcription have been completed and attached. It contains the full data about the call. This trigger should not be expected to be real-time and has a maximum delay of 20 minutes after the hangup before it fires.
- Phone Call Started
Triggers when an inbound phone call is started.
- SMS Received
Triggers when an SMS message is received.
- SMS Sent
Triggers when an SMS message is sent.
Trigger
New custom object recordPolling trigger: fires for each newly created record of a custom object type, newest first (HubSpot CRM v3 Search API sorted by createdate descending).
- Get custom object record
Retrieve a custom object record by ID. Optionally request specific properties.
- List custom object records
List records of a custom object type, paged. Optionally request specific properties and a page cursor.
- Search custom object records
Search records of a custom object type with filters, sorts, and a query (HubSpot CRM v3 Search API).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.