Integration
Connect Customer.guru to Relevance AI
When something happens in Customer.guru, your agent does the next thing in Relevance AI. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Customer.guru and Relevance AI 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 Customer.guru and Relevance AI
Triggers and actions 1 trigger · 7 actions
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.
Action
Get TaskGet a single task (conversation thread) by ID for an agent, including status and messages. Endpoint hint: Agent.getTask / task status polling.
- List Tasks
List tasks (conversation threads) for an agent, paginated/sortable/filterable by status. Endpoint hint: Agent.getTasks.
- Message Agent
Sends a message to an Agent. Doesn't wait for a response.
- Message Workforce
Sends a message to a Workforce. Doesn't wait for a response.
- Run Tool
Execute a Tool in Relevance AI. Waits for a response for up to 60 seconds.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.