Integration
Connect Givebutter to Rendi
When something happens in Givebutter, your agent does the next thing in Rendi. 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 Rendi 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 Rendi
Triggers and actions 4 triggers · 6 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.
Action
Delete FileDeletes one stored file in Rendi by file_id. DELETE /v1/files/{file_id}.
- Get File
Returns the details of one stored file — its status, download link, size, format and media properties.
- List Commands
Lists FFmpeg commands previously sent to Rendi. GET /v1/commands.
- Poll FFmpeg Command
Get the status of a previously submitted FFmpeg command
- Run FFmpeg Command
Submit an FFmpeg command for processing with input and output file specifications
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.