Sanaf AI
Start free
Fundraising

Givebutter, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Givebutter account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Fundraising
  • Connects with a key
  • 18 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Givebutter is

Givebutter is a fundraising platform that offers a free, open, and public API for developers to manage campaigns, track donations, and engage with supporters.

You paste in a key from your own Givebutter account. It is kept encrypted, and you can withdraw it from inside Givebutter whenever you like.

How a run works

One message in, the work done in Givebutter.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Givebutter. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Givebutter account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

18 tools it already has

What it can do in Givebutter

These are the ready-made tools your AI employee already has in Givebutter. It is not limited to them, but it never has to be taught these.

  • Archive ContactTool to archive a contact by their id. use after ensuring the contact has no associated data (e.g., no transactions or communications). example: "archive contact abc123".
  • Create CampaignTool to create a new campaign. use when you have title, description, goal, and type ready, after confirming your givebutter account is authenticated.
  • Create WebhookTool to create a new webhook subscription. use when you need to receive real-time notifications programmatically after confirming your endpoint can validate givebutter's signing se
  • Delete CampaignTool to delete a campaign by its id. use after confirming the campaign has no funds raised. example: "delete campaign abc123".
  • Delete ContactTool to delete a contact by their id. use after confirming the contact has no associated data (e.g., no transactions or communications). example: "delete contact abc123".
  • Delete FundTool to delete a fund by its id. use when you need to remove a fund after confirming it exists. example: "delete fund fund abc123".
  • Delete WebhookTool to delete a webhook by its id. use when you need to remove an obsolete webhook after confirming no further events are needed. example: "delete webhook abc123".
  • Get FundTool to retrieve details of a specific fund by its id. use after confirming the fund id is valid.
  • Get MembersTool to retrieve a paginated list of members for a given campaign. use when you need to list or process campaign members.
  • Get PayoutsTool to retrieve a list of payouts associated with your account. use when you need to list withdrawal transactions after authentication.
  • Get PlansTool to retrieve a list of plans associated with your account. use after authentication to fetch recurring donation plans.
  • Get TeamsTool to retrieve a list of teams for a specific campaign. use after creating or updating a campaign when you need to list fundraising teams. example: "get teams for campaign camp12
  • Get TicketsTool to retrieve a list of tickets. use when you need to list all tickets for your account after authentication.
  • Get TransactionsTool to retrieve a list of transactions associated with your account. use when you need to list all donations and payments, optionally filtered by scope.
  • Get WebhooksTool to retrieve all webhooks configured for your account. use after obtaining valid authentication.
  • Update CampaignTool to update an existing campaign's details by its id. use when you need to modify campaign attributes after creation.
  • Update ContactTool to update an existing contact's details by contact id. use when modifying contact information after confirming the contact id. only provided fields will be updated.
  • Update WebhookTool to update an existing webhook subscription's details. use when you need to modify a webhook's name, url, trigger events, or enabled state after confirming its id. example: "up
Access, and who is in charge of it

You stay the boss of your Givebutter account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Givebutter account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Givebutter is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Givebutter and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Givebutter

Can an AI employee really work inside Givebutter?
Yes. It signs in to your own Givebutter account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Givebutter?
No. Nothing moves and nothing is replaced. Your records stay in Givebutter, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Givebutter account?
You paste in a key from your own Givebutter account. It is kept encrypted, and you can withdraw it from inside Givebutter whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Givebutter?
It has 18 ready-made tools in Givebutter today, among them Archive Contact, Create Campaign and Create Webhook. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Givebutter and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Givebutter and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Givebutter?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Givebutter is written down with what it did and when.