# Givebutter integrations: campaigns and contacts

> Create a campaign, create a contact and create a transaction in Givebutter. Connect Givebutter to the rest of your finance stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/givebutter-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

Givebutter is a fundraising platform for nonprofits that runs donation campaigns, ticketed events and peer-to-peer fundraising, and keeps a donor CRM. Tray.ai connects to Givebutter through the HTTP Connector, so your workflows can call the Givebutter API alongside the rest of your stack.

## Use cases

### Campaigns

Read, create, update, and delete campaigns in Givebutter from any Tray.ai workflow. The Givebutter API covers calls such as list campaigns and create a campaign.

- List campaigns
- Create a campaign
- Get a campaign

### Contacts

Read, create, update, and delete contacts in Givebutter from any Tray.ai workflow. The Givebutter API covers calls such as list contacts and create a contact.

- List contacts
- Create a contact
- Update a contact

### Transactions

Read, create, and update transactions in Givebutter from any Tray.ai workflow. The Givebutter API covers calls such as list transactions and create a transaction.

- List transactions
- Create a transaction
- Get a transaction

### Funds

Read, create, update, and delete funds in Givebutter from any Tray.ai workflow. The Givebutter API covers calls such as list funds and create a fund.

- List funds
- Create a fund
- Update a fund

### Households

Read, create, update, and delete households in Givebutter from any Tray.ai workflow. The Givebutter API covers calls such as list households and create a household.

- List households
- Create a household
- Update a household

### Webhooks

Read, create, update, and delete webhooks in Givebutter from any Tray.ai workflow. The Givebutter API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

## Challenges Tray.ai solves

### Keeping Givebutter credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Givebutter credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Givebutter API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Givebutter API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Givebutter?

Yes. Tray.ai connects to Givebutter through the HTTP Connector, which calls the Givebutter API directly. Any call the Givebutter API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Givebutter?

The Givebutter API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Givebutter connector?

Givebutter runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Givebutter connector from the Givebutter API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/