Integration
Connect CallRail to Customer.guru
When something happens in CallRail, your agent does the next thing in Customer.guru. 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 Customer.guru 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 Customer.guru
Triggers and actions 6 triggers · 2 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 RatingTriggered when a customer submits a new rating on one of your Customer.guru surveys, giving you their score, their comment and how they engaged with the survey email.
- Find Customer
Looks up a customer in your Customer.guru account by email address and returns that customer's record — their id, when they were added, their most recent survey score and comment, and whether they have unsubscribed.
- Schedule Survey
Sends a Customer.guru NPS survey to one or more customers, either straight away or scheduled for a later date, and reports how many went out.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.