Integration

Givebutter integration

Givebutter is a fundraising platform for nonprofits. Manage campaigns (donation forms, peer-to-peer fundraisers, events), their discount codes, ticket types, teams and members; contacts with tags, activity timelines and households; funds; and webhooks. Read and record transactions (create_transaction records a gift and changes financial records, it charges nothing), and read payouts, recurring plans, pledges, issued tickets and sent messages. Webhook delivery logs, single-sign-on routes and editing a logged activity are not exposed; contact custom-field answers and the webhook signing secret are not returned. Authentication is an API key created in the Givebutter dashboard (Settings, Integrations, API Keys), sent as a Bearer token.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Givebutter.Built from the 63 Givebutter tools below, on the connection you add once.

What you can do with Givebutter

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 9 operations

  • add_household_contactAdd household contactPOSTAdds a contact to a household and returns the household.
  • create_contactCreate contactPOSTCreates a contact, or matches an existing one on email or phone (then the tags you send are added to it). Returns the contact with its id.
  • delete_contactDelete contactDELETEDeletes (archives) a contact; restore_contact brings an archived contact back.
  • get_contactGet contactGETReturns one contact: names, type, company and employer, emails, phones, addresses, social profiles, note, tags, giving stats, last donation, subscription flags and dates. Personal data.
  • get_household_contactGet household contactGETReturns one contact of a household: names, emails, phones, addresses, tags and giving stats. Personal data.
  • list_contactsList contactsGETLists contacts (donors, companies, supporters) with filters on type, dates, giving totals, email and name. Returns names, emails, phones, addresses, giving stats and tags. Personal data.
  • list_household_contactsList household contactsGETLists the contacts that belong to a household, with names, emails, phones, addresses and giving stats. Personal data.
  • remove_household_contactRemove household contactDELETERemoves a contact from a household and returns the household.
  • update_contactUpdate contactPUTUpdates a contact's fields, and can add or remove emails, phones and addresses. Sending tags REPLACES the whole tag set (an empty list clears it; leave tags out to keep them). Returns the contact.

Campaign, 5 operations

  • create_campaignCreate campaignPOSTCreates a campaign (a donation form, peer-to-peer fundraiser, event or general page) with a type and title, and returns it with its id, code and URL.
  • delete_campaignDelete campaignDELETEDeletes a campaign from the account. This cannot be undone through this API.
  • get_campaignGet campaignGETReturns one campaign: code, type, title, description, status, goal, amount raised, donor count, URL, cover, end date, event details (venue, dates, livestream) and settings.
  • list_campaignsList campaignsGETLists the account's campaigns: id, code, type, title, status, goal, amount raised, donor count, URL, event details and settings, with page links and totals.
  • update_campaignUpdate campaignPUTUpdates a campaign: type, title, texts, goal, end date, slug, published and public flags, cover or settings. Returns the updated campaign.

Fund, 5 operations

  • create_fundCreate fundPOSTCreates a fund (a designation donors can direct gifts to) and returns it with its id.
  • delete_fundDelete fundDELETEDeletes a fund from the account.
  • get_fundGet fundGETReturns one fund: name, code, amount raised and supporter count.
  • list_fundsList fundsGETLists the account's funds (designations donors can give to): name, code, amount raised and supporter count.
  • update_fundUpdate fundPUTRenames a fund or changes its code, and returns it.

Household, 5 operations

  • create_householdCreate householdPOSTCreates a household (a group of contacts treated as one family for giving) and returns it with its id.
  • delete_householdDelete householdDELETEDeletes a household record from the account.
  • get_householdGet householdGETReturns one household: name, head contact id, envelope name, note and its member contacts with names, emails and phones. Personal data.
  • list_householdsList householdsGETLists households (contacts grouped as one family) under data: name, head contact id, envelope name, note and member contacts with names, emails and phones. Page with page until no household comes back. Personal data.
  • update_householdUpdate householdPUTUpdates a household's name, head contact, envelope name or note, and returns it.

Ticket, 5 operations

  • create_ticket_typeCreate ticket typePOSTCreates a ticket type on a campaign (a ticket offer buyers can purchase) with a name and price, and returns it.
  • get_ticketGet ticketGETReturns one issued event ticket: attendee name, email and phone, ticket name, price, PDF link, transaction id, check-in time and answers to ticket questions. Personal data.
  • get_ticket_typeGet ticket typeGETReturns one ticket type of a campaign: name, description, price, retail price, quantity, subtype, active flag, bundles and pictures.
  • list_ticketsList ticketsGETLists issued event tickets: attendee name, email and phone, ticket name, price, PDF link, transaction id, check-in time and answers to ticket questions. Personal data.
  • list_ticket_typesList ticket typesGETLists the ticket types a campaign sells (the offers, not issued tickets): name, description, price, retail price, quantity, subtype, active flag, bundles and pictures.

Webhook, 5 operations

  • create_webhookCreate webhookPOSTCreates a webhook: Givebutter will POST the chosen events (gifts, contacts, campaigns, tickets, recurring plans, refunds) to your URL. Returns it with its id.
  • delete_webhookDelete webhookDELETEDeletes a webhook; Givebutter stops sending its events.
  • get_webhookGet webhookGETReturns one webhook: name, target URL, subscribed events, enabled flag, last delivery status and when it was last used.
  • list_webhooksList webhooksGETLists the account's webhooks: name, target URL, subscribed events, enabled flag, last delivery status and when it was last used.
  • update_webhookUpdate webhookPUTUpdates a webhook's URL, events (both required), name or enabled flag, and returns it.

Activity, 4 operations

  • create_contact_activityCreate contact activityPOSTLogs an activity on a contact's timeline: a record of a note, email, meeting, phone call, text, completed task or volunteer activity that happened. Returns the activity.
  • delete_contact_activityDelete contact activityDELETEDeletes an activity from a contact's timeline.
  • get_contact_activityGet contact activityGETReturns one activity of a contact's timeline: type, source, text, the related record (transaction, plan, ticket or message), who logged it and when it occurred.
  • list_contact_activitiesList contact activitiesGETLists a contact's activity timeline: logged notes, calls, meetings and emails plus system events such as gifts, tickets, subscriptions and tag changes, each with its related record.

Discount code, 4 operations

  • create_discount_codeCreate discount codePOSTCreates a discount code on a campaign (a percent or fixed amount off at checkout, for example on event tickets) and returns it.
  • delete_discount_codeDelete discount codeDELETEDeletes a discount code from a campaign; it can no longer be used at checkout.
  • list_discount_codesList discount codesGETLists the discount codes of a campaign: code, type (percentage or fixed), amount, how many times used and allowed, active flag, validity dates and total discount given.
  • update_discount_codeUpdate discount codePUTUpdates a campaign discount code (amount is required; code, type, active flag, use limit, dates and items are optional) and returns it.

Transaction, 4 operations

  • create_transactionCreate transactionPOSTRecords a gift received by check, cash, card or another method as a transaction in Givebutter's financial records; no payment is charged. Returns the transaction with its id.
  • get_transactionGet transactionGETReturns one transaction: donor details, campaign, team, member, fund, amount, fees, donated and payout amounts, method, status, dedication, line items, check details and dates. Personal data.
  • list_transactionsList transactionsGETLists donation and payment transactions with date, method and deposit filters: donor details, campaign, fund, amount, fees, payout, method, status, dedication and line items. Personal data.
  • update_transactionUpdate transactionPUTUpdates a transaction's internal note, check number and deposit date, campaign, team, member, fund, method, date or dedication. Changes financial records. Returns the transaction.

Team, 3 operations

  • delete_campaign_teamDelete campaign teamDELETEDeletes a fundraising team from a campaign.
  • get_campaign_teamGet campaign teamGETReturns one fundraising team of a campaign: name, logo, slug, page URL, amount raised, goal, supporter and member counts.
  • list_campaign_teamsList campaign teamsGETLists a campaign's fundraising teams: name, logo, slug, page URL, amount raised, goal, supporter and member counts.

Member, 2 operations

  • list_campaign_membersList campaign membersGETLists a campaign's members (peer-to-peer fundraisers): name, display name, email, phone, picture, amount raised, goal, donor count and personal page URL. Personal data.
  • remove_campaign_memberRemove campaign memberDELETERemoves a member (a peer-to-peer fundraiser) from a campaign.

Message, 2 operations

  • get_messageGet messageGETReturns one email or text message sent from Givebutter: channel, status, internal name, subject, preheader, body, recipient filters and count, and send dates.
  • list_messagesList messagesGETLists the email and text messages sent or scheduled from Givebutter: channel, status, internal name, subject, body, recipient filters and count, and send dates.

Payout, 2 operations

  • get_payoutGet payoutGETReturns one payout (money Givebutter paid out to the account): campaign, method, status, gross amount, fees, tips, net payout, currency, address, memo and dates.
  • list_payoutsList payoutsGETLists payouts (money Givebutter paid out to the account): campaign, method, status, gross amount, fees, tips, net payout, currency, address, memo and dates.

Plan, 2 operations

  • get_recurring_planGet recurring planGETReturns one recurring donation plan: donor, frequency, status, payment method, amount, fee covered, start date, next bill date and cancel date. Personal data.
  • list_recurring_plansList recurring plansGETLists recurring donation plans: donor contact id, name, email and phone, frequency, status, payment method, amount, fee covered, start date, next bill date and cancel date. Personal data.

Pledge, 2 operations

  • get_pledgeGet pledgeGETReturns one pledge (a promised gift): contact, campaign and fund ids, status, amount pledged, fulfilled and remaining, installment schedule, reminders, memo and dates.
  • list_pledgesList pledgesGETLists pledges (promised gifts): contact, campaign and fund ids, type, status, amount pledged, fulfilled and remaining, installment schedule, memo and dates.

Add, 1 operation

  • add_contact_tagsAdd contact tagsPOSTAdds tags to a contact, keeping the tags it already has. Returns the contact.

Remove, 1 operation

  • remove_contact_tagsRemove contact tagsPOSTRemoves the listed tags from a contact, keeping the others. Returns the contact.

Restore, 1 operation

  • restore_contactRestore contactPATCHRestores a contact that was deleted (archived) and returns it.

Sync, 1 operation

  • sync_contact_tagsSync contact tagsPOSTReplaces a contact's whole tag set with exactly the tags sent (any tag not listed is removed). Returns the contact.

Use Givebutter from Claude Code, Cursor or Codex

Connect Givebutter in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Givebutter operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Givebutter

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Givebutter once

    Add your Givebutter connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Givebutter integration FAQ

What can you do with the Givebutter integration?

LiveContext exposes 63 operations on Givebutter, covering contact, campaign, fund and household.

Popular integrations

Browse the whole catalog