Connect Givebutter
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Givebutter account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Givebutter. Only the status word and the order number.
Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.
This connects your own Givebutter account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Givebutter. Only the status word and the order number are ever texted back, never names, prices, items or addresses.
TIP: You need about 15 minutes, a computer, and the sign-in for your Givebutter account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.
NOTE: This guide was written from Givebutter's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Givebutter account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.
Who this is for: nonprofit community. How Givebutter gives access: You create the key yourself in your own account; no approval is needed. What it costs you: The docs do not state a price or plan requirement for API keys.
Part 1. Get your key from Givebutter
Do this on your computer, in a new browser tab, signed in to Givebutter.
- Sign in to Givebutter as an account admin.
- Open [[Settings > Integrations > API Keys]].
- Press Create New API Key and give it the name Speakvora.
- Copy the key immediately, because Givebutter shows it only once.
- Paste the key into Speakvora and press Test connection.
- Speakvora only reads transactions and campaigns and never changes anything.
WARNING: If Givebutter asks which permissions to give, tick only the read-only ones: API key: read access to transactions and campaigns (the docs do not describe scopes; only GET calls are made). Never give write or admin access.
TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.
Part 2. Open the Connect tab in your agent
- Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
- Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
- Under Your apps type Givebutter in the box that says Find an app (1), or scroll down the list.
- Press Givebutter. A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)



Part 3. Paste it in
1 box to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:
- Givebutter API key (secret: it stays on this computer and is never shown again, only the last few characters). Settings > Integrations > API Keys > Create New API Key. It is shown only once, so copy it right away.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.
Part 4. Test it
- Press the orange Save and test button.
- Givebutter is asked for one harmless record, just to prove the key works. Nothing is changed in Givebutter.

YOU SHOULD SEE: green words starting with Connected.
WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.
What happens next
- A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Givebutter), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Givebutter is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Givebutter when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Givebutter. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
- It cannot find an order (404): the number is not in Givebutter, or Givebutter uses a longer number than the one on the receipt.
- It says too many requests (429): wait a minute and press Save and test again.
- Givebutter says you need a plan or approval: The docs do not list the possible values of a transaction's status, so none are mapped. The transaction id is the transaction's tid string. Ticket lookups need a campaign id and are not used here.
- Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.
If your plan has no API
- Export transactions from the Givebutter dashboard as a CSV if you cannot create an API key.
Givebutter's own instructions: https://docs.givebutter.com/api-reference/authentication
All help guides · Every agent feature · AI receptionist by industry
Questions
What if this happens: It says the key was refused (401 or 403)?
copy the key again from Givebutter. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
What if this happens: It cannot find an order (404)?
the number is not in Givebutter, or Givebutter uses a longer number than the one on the receipt.
What if this happens: It says too many requests (429)?
wait a minute and press Save and test again.
What if this happens: Givebutter says you need a plan or approval?
The docs do not list the possible values of a transaction's status, so none are mapped. The transaction id is the transaction's tid string. Ticket lookups need a campaign id and are not used here.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.