Overview
The Patreon Trigger node for n8n starts workflows in response to specific events occurring on a Patreon campaign. It listens for webhook notifications from Patreon, such as when members are created or deleted, pledges are updated, or posts are published or removed. This node is useful for automating actions based on Patreon activity, such as updating CRM records, sending notifications, or managing community access.
Example scenarios:
- Automatically add new patrons to a mailing list when they join.
- Remove users' access when their membership is deleted.
- Notify your team when a new post is published on your Patreon campaign.
Properties
| Name | Type | Meaning |
|---|---|---|
| Events | options | The type of Patreon event that will trigger the workflow. Options include member creation/deletion, pledge updates, and post changes. |
| Campaign ID | string | The unique identifier of the Patreon campaign for which you want to receive event notifications. |
Output
The node outputs a single item per webhook event with the following structure:
[
{
"body": { /* Raw payload sent by Patreon for the selected event */ },
"headers": { /* HTTP headers received with the webhook request */ },
"query": { /* Query parameters (if any) included in the webhook URL */ }
}
]
- body: Contains the full JSON payload from Patreon describing the event.
- headers: All HTTP headers sent with the webhook request.
- query: Any query parameters present in the webhook call.
Dependencies
- External Service: Requires a Patreon account and an active campaign.
- API Credentials: Needs OAuth2 credentials for the "patreonOAuth2Api" in n8n.
- Webhook Configuration: The node automatically registers and manages webhooks with Patreon for the specified campaign and event.
Troubleshooting
Common Issues:
- Invalid Campaign ID: If the provided Campaign ID is incorrect, the webhook registration will fail.
- Missing Permissions: Ensure the connected Patreon account has permission to manage webhooks for the campaign.
- Webhook Not Triggering: Make sure the webhook URL is accessible from the internet and not blocked by firewalls.
Error Messages:
- 401 Unauthorized / 403 Forbidden: Check your OAuth2 credentials and permissions.
- 404 Not Found: Verify the Campaign ID is correct and exists.
- Webhook Already Exists: The node attempts to clean up old webhooks before creating a new one, but manual intervention may be needed if issues persist.