How to connect Givebutter to OpenClaw
Connect Givebutter to OpenClaw with ClawLink: paste your Givebutter key once and 58 tools work from chat. No MCP server to run, nothing stored on your machine.
GivebutterAPI KEYMCPGivebutter is a fundraising platform that offers a free, open, and public API for developers to manage campaigns, track donations, and engage with supporters.. Once connected, OpenClaw can read and act on Givebutter from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Givebutter access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Givebutter setup: install one ClawHub skill, connect Givebutter in the browser, and OpenClaw can call real Givebutter actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Givebutter.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Givebutter
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Givebutter?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Givebutter in the ClawLink dashboard — paste your Givebutter API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Givebutter, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Givebutter is connected in the dashboard, that agent calls the same 58 Givebutter tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Givebutter MCP for OpenClaw
Looking for a Givebutter MCP server for OpenClaw? ClawLink connects Givebutter to OpenClaw and exposes 58 Givebutter tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Givebutter integration works the same way.
What the OpenClaw Givebutter integration can do
58 Givebutter tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 58.
30 of 58 Givebutter tools for OpenClaw
| Tool | What it does |
|---|---|
Get campaign givebutter_get_campaign | Retrieve details for a specific campaign by its ID or code |
Get campaign ticket givebutter_get_campaign_ticket | Retrieve a specific campaign ticket by campaign ID and ticket ID |
Get contact givebutter_get_contact | Retrieve details of a specific contact by ID |
Get contact activity givebutter_get_contact_activity | Retrieve a specific contact activity by contact ID and activity ID |
Get discount code givebutter_get_discount_code | Retrieve details of a specific discount code for a campaign |
Get fund givebutter_get_fund | Retrieve details of a specific fund by its ID |
Get household givebutter_get_household | Retrieve details of a specific household by its ID |
Get members givebutter_get_members | Retrieve a paginated list of members for a given campaign |
Get payouts givebutter_get_payouts | Retrieve a list of payouts associated with your account |
Get plans givebutter_get_plans | Retrieve a list of plans associated with your account |
Get teams givebutter_get_teams | Retrieve a list of teams for a specific campaign |
Get tickets givebutter_get_tickets | Retrieve a list of tickets |
Get transactions givebutter_get_transactions | Retrieve a list of transactions associated with your account |
Get webhook givebutter_get_webhook | Retrieve a specific webhook by its ID |
Get webhook activity givebutter_get_webhook_activity | Retrieve a specific webhook activity by its ID |
Get webhooks givebutter_get_webhooks | Retrieve all webhooks configured for your account |
List campaign tickets givebutter_list_campaign_tickets | Retrieve a list of all campaign tickets for a specific campaign |
List campaigns givebutter_list_campaigns | Retrieve a paginated list of campaigns for the authenticated account |
List contact activities givebutter_list_contact_activities | Retrieve all activities for a specific contact |
List contacts givebutter_list_contacts | Retrieve a paginated list of contacts from your Givebutter account |
List discount codes givebutter_list_discount_codes | List all discount codes for a campaign |
List funds givebutter_list_funds | List all funds in your Givebutter account |
List household contacts givebutter_list_household_contacts | Retrieve all contacts associated with a household |
List households givebutter_list_households | Retrieve a list of all households in your account |
List messages givebutter_list_messages | Retrieve a paginated list of messages |
List pledges givebutter_list_pledges | Retrieve a paginated list of all pledges |
List webhook activities givebutter_list_webhook_activities | List all webhook activities for a specific webhook |
Add contact tags givebutter_add_contact_tags | Add tags to a contact by contact ID |
Add household contact givebutter_add_household_contact | Add a contact to a household |
Create campaign givebutter_create_campaign | Create a new campaign |
Try it: find the Givebutter tool you need
Browse the 30 Givebutter tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Givebutter, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Givebutter, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Givebutter, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Givebutter, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Givebutter working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Givebutter API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Givebutter account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Givebutter. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Givebutter actions to the runtime in a format your agent can reliably use. | 58 tools for Givebutter are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Givebutter to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Givebutter in the browser, and the 58 tools above work from chat. There is no SDK and no config file, and the Givebutter key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Givebutter skill but can't call the tools
The ClawHub skill teaches OpenClaw about Givebutter, but the calls run through the ClawLink plugin and your connected account. Make sure Givebutter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Givebutter from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Givebutter tools
Givebutter tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Givebutter call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Givebutter returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Givebutter has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Givebutter integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Givebutter: link your Givebutter account once in the browser and OpenClaw can call the Givebutter API through 58 ready-made tools — no custom code or token handling.
How do I add Givebutter to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Givebutter skill from ClawHub, then you click Connect in the dashboard to authorize Givebutter. OpenClaw calls the tools from the next message — no config files, and the Givebutter key you paste is stored server-side instead of in your environment.
How long does it take to connect Givebutter to OpenClaw?
About two minutes. Sign in, click Connect next to Givebutter in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Givebutter up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Givebutter working from chat.
OpenClaw installed the Givebutter skill but can't call the tools
The ClawHub skill teaches OpenClaw about Givebutter, but the calls run through the ClawLink plugin and your connected account. Make sure Givebutter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
Connect GitHub
Manage repositories, issues, pull requests, and workflows
Connect PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.