Integration
Connect SignWell to Givebutter
When something happens in SignWell, your agent does the next thing in Givebutter. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want SignWell and Givebutter 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 SignWell and Givebutter
Triggers and actions 7 triggers ยท 2 actions
Trigger
Document CompletedTriggers when a document has been completed.
- Document Sent
Triggers when a document is sent.
- Document Viewed
Triggers when a signer views a document for the first time.
- Create Document From Template
Creates a document from a template and sends the document. This action uses API requests. Limits apply if not using an API plan.
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.
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