Patreon icon

Patreon

Consume Patreon API

Overview

This node allows you to retrieve a specific post from Patreon by its Post ID. It is useful in scenarios where you need to fetch detailed information about a single Patreon post, such as displaying post content, checking publication status, or integrating Patreon post data into other workflows. For example, you might use this node to automatically archive new posts, analyze post engagement, or trigger notifications when a particular post is published.

Properties

Name Type Meaning
Post ID String Patreon post ID (required). This is the unique identifier of the post you want to retrieve from Patreon.

Output

The output is a JSON object containing details about the requested Patreon post. The structure includes the following fields:

  • title: The title of the post.
  • content: The main content/body of the post.
  • is_paid: Boolean indicating if the post is paid-only.
  • is_public: Boolean indicating if the post is public.
  • published_at: Timestamp of when the post was published.
  • url: Direct URL to the post.
  • embed_data: Any embed data associated with the post.
  • embed_url: URL for embedded content.
  • app_id: Application ID if applicable.
  • app_status: Status of the application if relevant.

All output is in JSON format; binary data is not returned by this operation.

Dependencies

  • Patreon OAuth2 API credentials are required. You must configure the patreonOAuth2Api credential in n8n to authenticate requests.
  • No additional environment variables are needed beyond standard n8n and Patreon API setup.

Troubleshooting

  • Invalid Post ID: If an incorrect or non-existent Post ID is provided, the node will throw an error. Ensure the Post ID exists and is accessible with your credentials.
  • Authentication Errors: If your OAuth2 credentials are missing or invalid, you may receive authentication errors. Double-check your n8n credential configuration.
  • API Rate Limits: Patreon may enforce rate limits. If you encounter rate limit errors, try reducing the frequency of your requests.

Links and References

Discussion