Actions12
Publish Image to Workspace
AI-generatedSummary
Publish an image to social media platforms via a specified workspace, optionally attaching up to five post-publish comments across enabled platforms (Facebook, Instagram, YouTube; TikTok comments are not supported).
Inputs
- Workspace ID (required) — The ID of the workspace under which to publish the image.
- Image Source (required) — Select whether the image is specified by an External URL or an Uploaded Bucket File.
- Image URL (required) — If 'External URL' is selected, provide a publicly reachable URL of the image to publish.
- Bucket File URL (required) — If 'Uploaded Bucket File' is selected, provide the fileURL returned by a prior /generate-upload-urls upload operation.
- Upload Post ID — Optional postId returned alongside the Bucket File URL to associate ownership of the uploaded image; if omitted, the image is not automatically deleted later.
- Caption (required) — Shared caption used as the default per-platform description (1 to 8000 characters). Platform-specific overrides may still apply.
- AI-Enhanced — Boolean flag indicating if the caption is AI-enhanced; this information surfaces only on the status page.
- Comments — Up to five comments to post under each enabled platform after publishing. Each comment may include text (1-2200 characters), optional delay in minutes (0-1440), and an optional image URL (Facebook only). Specify which platforms receive each comment (Facebook, Instagram, YouTube). TikTok comments are never supported and will be reported as "notSupported".
Output shape
a single record representing the created image post with publish and comment status response.
The operation requires valid 'posty5Api' credentials with an API key. Posting consumes credits: 50 credits per image post plus 25 credits per comment that actually posts. The API endpoint used depends on whether publishing to workspace or account and on image source type, with automatic management of uploaded file lifecycles if Upload Post ID is provided. Comments submitted via the now-deprecated singular 'Comment' input are internally mapped to the first entry of 'Comments' if the latter is empty; both are never used simultaneously in the request.