Postiz icon

Postiz

Consume Postiz API

Actions4

Overview

This node integrates with the Postiz API to manage social media posts and related content. Specifically, the Get Posts operation retrieves a list of posts filtered by various time parameters (week, day, month, year) and optionally by customer ID. This is useful for scenarios where you want to fetch scheduled or published posts for reporting, analytics, or further processing in an automation workflow.

Practical examples include:

  • Fetching all posts scheduled for a specific week to generate a weekly report.
  • Retrieving posts for a particular day to analyze daily engagement.
  • Filtering posts by customer to monitor activity per client.

Properties

Name Meaning
Week Week number (1-52) to filter posts by week of the year.
Day Day number (0-6) to filter posts by day of the week, where 0 represents Sunday.
Display Display mode for posts; options are: day, week, or month.
Month Month number (1-12) to filter posts by month.
Year Year (2022-2035) to filter posts by year.
Customer Optional customer ID string to filter posts belonging to a specific customer.

Output

The output is a JSON array containing the list of posts matching the specified filters. Each post object includes details as returned by the Postiz API, such as post content, scheduling information, tags, integrations, and other metadata.

No binary data is output for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Postiz API.
  • The node uses an internal helper function to make HTTP requests to the Postiz API endpoints.
  • No additional external dependencies beyond the Postiz API and standard n8n environment.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Providing out-of-range values for week (not between 1-52), day (not between 0-6), month (not between 1-12), or year (outside allowed range) may result in API errors or empty results.
    • If filtering by customer ID, ensure the ID is valid and exists in the Postiz system.

  • Error messages:

    • Errors from the API are caught and returned as part of the node output with an error field describing the issue.
    • Common error descriptions include invalid parameters, unauthorized access, or resource not found.

  • Resolution tips:

    • Verify that all input parameters conform to their expected ranges and formats.
    • Check that the API key credential is correctly configured and has necessary permissions.
    • Review the Postiz API documentation for any changes or limitations on filtering parameters.

Links and References

Discussion