Integration
Connect Givebutter to Basin
When something happens in Givebutter, your agent does the next thing in Basin. 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 Basin 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 Basin
Triggers and actions 5 triggers ยท 12 actions
Trigger
New CampaignTriggers when a new campaign is created.
- New Ticket
Triggers when a new ticket is issued.
- New Transaction
Triggers when a new transaction is created.
- Updated Campaign
Triggers when a campaign is updated.
- Create Contact
Creates 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 SubmissionTriggers when your form receives a submission.
- Add form
Create a new form under a project. POST /api/v1/forms.
- Add project
Create a new project (form-organizing container). POST /api/v1/projects.
- Delete form
Destroy a form. DELETE /api/v1/forms/:id.
- Delete submission
Destroy a submission. DELETE /api/v1/submissions/:id.
- Get form
Retrieve a single form by id. GET /api/v1/forms/:id.
- Get submission
Retrieve a single submission by id. GET /api/v1/submissions/:id.
- List forms
List all forms accessible to the account. GET /api/v1/forms.
- List projects
List all projects accessible to the account. GET /api/v1/projects.
- List submissions
List submissions for a form. GET /api/v1/submissions.
- Update form
Update a form's configuration (notifications, spam protection, branding, etc). PATCH/PUT /api/v1/forms/:id.
- Update submission
Update a submission's state fields (spam, read, trash). PATCH/PUT /api/v1/submissions/:id.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews