Integration
Connect Givebutter to Customer.guru
When something happens in Givebutter, 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 Givebutter 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 Givebutter and Customer.guru
Triggers and actions 5 triggers · 3 actions
Trigger
New CampaignTriggers when a new campaign is created.
Trigger
New TicketTriggers when a new ticket is issued.
Trigger
New TransactionTriggers when a new transaction is created.
Trigger
Updated CampaignTriggers when a campaign is updated.
Action
Create ContactCreates a Contact. If there is a contact that already exists with the same First and Last Name, as well as the same Email Or Phone, we will automatically deduplicate and merge the contact, otherwise a new contact will be created. If you'd like to always create a new contact regardless of the deduplication logic, pass the force_create parameter as true.
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.
Action
Find CustomerLooks 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.
Action
Schedule SurveySends 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.