Actions6
- Campaign Actions
- Member Actions
- Post Actions
Overview
The "Get All Members" operation for the "Member" resource in this custom n8n Patreon node retrieves a list of all members associated with a specified Patreon campaign. This is useful for creators or administrators who want to automate the process of fetching supporter/member data from their Patreon campaigns, such as for analytics, CRM integration, or personalized communication.
Practical examples:
- Syncing Patreon member lists with an email marketing tool.
- Generating reports on current supporters and their tiers.
- Automating fulfillment processes (e.g., shipping rewards) based on member addresses.
Properties
| Name | Type | Meaning |
|---|---|---|
| Campaign ID | String | Patreon campaign ID. Required to specify which campaign's members to retrieve. |
Output
The output is a JSON array where each item represents a Patreon member with detailed information. The structure includes:
- full_name: The full name of the member.
- 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 by the member in cents.
- currently_entitled_amount_cents: Current monthly pledge amount in cents.
- patron_status: Status of the patron (e.g., active_patron, former_patron).
- currently_entitled_tiers: Array of tier objects, each including:
- amount_cents
- created_at
- description
- discord_role_ids
- edited_at
- patron_count
- published
- published_at
- requires_shipping
- title
- url
- address: Object containing:
- addressee
- city
- line_1
- line_2
- phone_number
- postal_code
- state
Note: If any binary data is present (e.g., images), it will be referenced via URLs in the JSON, not as direct binary output.
Dependencies
- External Service: Requires access to the Patreon API.
- Authentication: Needs a valid OAuth2 credential set up in n8n (
patreonOAuth2Api). - Environment/Configuration: Ensure that the connected Patreon account has permission to access the specified campaign.
Troubleshooting
Common Issues:
- Invalid Campaign ID: If the provided Campaign ID is incorrect or does not exist, the node will throw an error.
- Missing Credentials: If OAuth2 credentials are not configured, the node will fail to authenticate.
- Insufficient Permissions: If the authenticated Patreon account lacks access to the campaign, the request will fail.
Error Messages & Resolutions:
"Request failed with status code 404": Check that the Campaign ID is correct and exists."401 Unauthorized": Verify that your OAuth2 credentials are valid and have not expired."403 Forbidden": Ensure the authenticated user has access to the campaign.