Integration
Connect Beanstalk to Customer.guru
When something happens in Beanstalk, 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 Beanstalk 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 Beanstalk and Customer.guru
Triggers and actions 3 triggers · 9 actions
Trigger
New RepositoryPolls for newly created repositories.
- New User
Polls for newly added users.
- Add public key
Add an SSH public key for Git authentication. POST /api/public_keys.json with name, content (single public SSH key).
- Create Repository
Create a new repository in the Beanstalk account.
- Get Repository
Retrieve a single repository by ID.
- Get User
Retrieve a single user by ID.
- List public keys
List SSH public keys for users on the account. GET /api/public_keys.json (optional user_id for admins).
- List Repositories
List all repositories in the Beanstalk account.
- List Users
List all users in the Beanstalk account.
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.