Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Postiz

Open-source social media scheduling tool supporting 30+ platforms

CategoryMarketing
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Postiz with Flows360

Open-source social media scheduling tool supporting 30+ platforms

Use the Postiz connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 9 actions and 1 trigger.

Available actions

  • Create Post
  • List Posts
  • Delete Post
  • List Channels
  • Find Available Slot
  • Get Platform Analytics
  • Get Post Analytics
  • Upload File from URL
  • Plus 1 additional declared action.

Available triggers

  • New Published Post

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Postiz
  • Package: @activepieces/piece-postiz@0.1.0
  • Exact artifact digest: sha256:ba308040ebdf1b40159e4fe15d21b9c8f2362203101b6c5315663c53ded03ceb
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Post (create_post), Create or schedule a post on one or more connected channels Classification: read.
  • List Posts (list_posts), Retrieve posts within a date range Classification: read.
  • Delete Post (delete_post), Delete a post and all other posts in the same group Classification: read.
  • List Channels (list_integrations), List all connected social media channels in your organization Classification: read.
  • Find Available Slot (find_available_slot), Find the next available posting time slot for a connected channel Classification: read.
  • Get Platform Analytics (get_platform_analytics), Retrieve analytics (followers, impressions, engagement) for a connected channel Classification: read.
  • Get Post Analytics (get_post_analytics), Retrieve analytics (likes, comments, shares, impressions) for a specific published post Classification: read.
  • Upload File from URL (upload_file_from_url), Upload a media file from a URL to Postiz. Returns the file path to use when creating posts. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Published Post, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects10
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Base URL Required
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Post Yes No Create or schedule a post on one or more connected channels
List Posts Yes No Retrieve posts within a date range
Delete Post Yes No Delete a post and all other posts in the same group
List Channels Yes No List all connected social media channels in your organization
Find Available Slot Yes No Find the next available posting time slot for a connected channel
Get Platform Analytics Yes No Retrieve analytics (followers, impressions, engagement) for a connected channel
Get Post Analytics Yes No Retrieve analytics (likes, comments, shares, impressions) for a specific published post
Upload File from URL Yes No Upload a media file from a URL to Postiz. Returns the file path to use when creating posts.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Published Post Yes No polling trigger declared by the pinned package.

Triggers

New Published Post · Poll

Triggers when a post is published in Postiz

Setup

Setup

  1. Add the Postiz connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Base URL (base_url), required.
  • API Key (api_key), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-postiz@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Postiz connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-postiz@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com