# Patreon integrations: campaigns and posts

> Start a Tray.ai workflow when Patreon sends “Member created”. Connect Patreon to the rest of your e-commerce stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/patreon-integrations/
**Categories:** E-commerce
**Connects through:** HTTP Connector

## Overview

Patreon is a membership platform where creators run paid tiers for supporters and share posts and live content with their members. Tray.ai connects to Patreon through the HTTP Connector, so your workflows can call the Patreon API alongside the rest of your stack.

## Use cases

### Campaigns

Read campaigns in Patreon from any Tray.ai workflow. The Patreon API covers calls such as list campaigns and get a campaign.

- List campaigns
- Get a campaign

### Members

Read members in Patreon from any Tray.ai workflow. The Patreon API covers calls such as list campaign members and get a member.

- List campaign members
- Get a member

### Posts

Read posts in Patreon from any Tray.ai workflow. The Patreon API covers calls such as list campaign posts and get a post.

- List campaign posts
- Get a post

### Webhooks

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

- List webhooks
- Create a webhook
- Update a webhook

### Patreon events

Start a Tray.ai workflow the moment something happens in Patreon. Patreon sends events such as member created and member updated to a Tray.ai webhook trigger.

- Member created
- Member updated
- Member deleted

## Challenges Tray.ai solves

### Keeping Patreon 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 Patreon 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 Patreon 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 Patreon 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 Patreon?

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

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

The Patreon API uses OAuth 2.0 and 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 Patreon connector?

Patreon runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Patreon connector from the Patreon 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/