Actions6
- Campaign Actions
- Member Actions
- Post Actions
Overview
This n8n node interacts with the Patreon API to retrieve information about a specific member. In the context of the "Member" resource and the "Get a Member" operation, the node fetches detailed data for a single Patreon member using their unique Member ID. This is useful for workflows that need to look up supporter details, verify membership status, or personalize communications based on Patreon membership data.
Example scenarios:
- Fetching a member's current pledge status to grant access to exclusive content.
- Retrieving shipping address information for sending physical rewards.
- Checking if a user is an active patron before processing further automation steps.
Properties
| Name | Type | Meaning |
|---|---|---|
| Member ID | String | Patreon member ID (required). Used to identify and fetch details for a specific member. |
Output
The node outputs a JSON object containing detailed information about the specified Patreon member. The structure includes:
- full_name: The member's full name.
- is_follower: Boolean indicating if the user is only following (not pledging).
- last_charge_date: Date of the last successful charge.
- last_charge_status: Status of the last charge (e.g., Paid, Declined).
- lifetime_support_cents: Total amount supported in cents.
- currently_entitled_amount_cents: Current monthly pledge amount in cents.
- patron_status: Membership status (e.g., active_patron, former_patron).
- currently_entitled_tiers: Array of tiers the member is currently entitled to, each with:
- amount_cents
- created_at
- description
- discord_role_ids
- edited_at
- patron_count
- published
- published_at
- requires_shipping
- title
- url
- address: Shipping address details, including:
- addressee
- city
- line_1
- line_2
- phone_number
- postal_code
- state
Note: The output does not include binary data; all information is returned as structured JSON.
Dependencies
- Patreon OAuth2 API credentials are required. You must configure the
patreonOAuth2Apicredential in n8n. - Access to the Patreon API via a valid connected account.
Troubleshooting
Common issues:
- Invalid Member ID: If the provided Member ID does not exist or is incorrect, the node will throw an error from the Patreon API.
- Missing Credentials: If the OAuth2 credentials are not set up or have expired, authentication errors will occur.
- Insufficient Permissions: The connected Patreon account must have permission to access the requested member data.
Error messages and resolutions:
"Request failed with status code 404": The Member ID is invalid or does not exist. Double-check the ID."401 Unauthorized": Check your OAuth2 credentials and ensure they are correctly configured and have not expired."403 Forbidden": The authenticated user does not have access to this member's data. Ensure the correct campaign and permissions.