Postiz icon

Postiz

Consume Postiz API

Actions4

Overview

This node integrates with the Postiz API to manage social media posts and related content. It supports creating, scheduling, deleting posts, retrieving posts and integrations, and uploading files. The "Create Post" operation allows users to create posts immediately, as drafts, or scheduled for a future date, including rich content such as text, images, tags, and provider-specific settings.

Common scenarios include:

  • Automating social media publishing workflows by scheduling posts across multiple channels.
  • Managing post drafts and immediate publishing.
  • Uploading media files to be attached to posts.
  • Retrieving existing posts or connected integrations for reporting or further automation.

Practical example: A marketing team can use this node to schedule a campaign post with multiple tagged topics, targeted to different social media channels, each with customized settings and multimedia content.

Properties

Name Meaning
Type Type of post to create. Options: Draft (save as draft), Schedule (post at a specified future date/time), Now (post immediately).
Short Link Boolean flag indicating whether to use short links in the post content.
Date Date and time for the post. Required for scheduling or immediate posting; ignored for drafts.
Tags Array of tags for the post. Each tag has a Value (tag value) and Label (tag label).
Posts Array of posts to create (required for non-draft types). Each post includes:
- Integration ID: Identifier of the integration/channel where the post will be published.
- Group: Optional grouping of the post.
- Settings: Provider-specific key-value pairs.
- Content Items: Array of content items, each with:
  • Content text
  • Optional content ID
  • Images array, each image with an ID and path/URL.

Output

The node outputs JSON data representing the response from the Postiz API for the requested operation.

For the "Create Post" operation, the output JSON contains details about the created post(s), including their IDs, status, and any metadata returned by the API.

If an error occurs, the output JSON contains an error field with the error message or description.

The node does not output binary data for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Postiz API.
  • Uses the Postiz REST API endpoints for posts, integrations, and file uploads.
  • For file uploads, it uses multipart form-data encoding.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication errors.
    • Providing incomplete or incorrectly formatted post data (e.g., missing required fields like Integration ID or content) may result in API validation errors.
    • Scheduling posts with invalid dates or past timestamps might be rejected by the API.
    • Uploading files without specifying the correct binary property name or file extension can cause upload failures.

  • Error messages:

    • Errors returned from the API are captured and included in the output under an error field.
    • Network or connectivity issues will throw exceptions logged to the console and returned as error messages.

  • Resolution tips:

    • Ensure all required properties are set correctly according to the operation.
    • Validate date/time values before scheduling posts.
    • Confirm that the binary property used for file uploads contains valid base64-encoded data.
    • Check API key permissions and validity.

Links and References

Discussion