Social Media Publisher

• postplus-shared

  release-shell rules

• guiding users through the invite-link channel onboarding flow
• listing integrations available on the PostPlus Postiz workspace
• preparing a local publish request draft
• creating a Postiz draft or schedule only after explicit approval
• promoting an existing Postiz draft into the queue only after a second approval

Ownership model

1. the product calls

   GET /public/v1/social/{integration}

   with the PostPlus Postiz API key
2. Postiz returns a social-platform OAuth URL (e.g. Instagram, TikTok) and stores a state → PostPlus org mapping in Redis for 1 hour
3. the product delivers that URL to the end user (via UI or CLI)
4. the user clicks the link and authorizes their social account on the platform's own OAuth consent screen — no Postiz registration required
5. the resulting channel token lands in the PostPlus Postiz org
6. the product labels the channel with the user's PostPlus account id via

   PUT /integrations/:id/customer-name

Safe default

create_post.mjs

--execute

• validates the local request
• enforces the integration allowlist
• writes a local preview envelope
• emits an

  approvalRequest

• does not call Postiz

• --execute

• --approval-file <approved.json>

• a channel that has been onboarded via the invite-link flow above

change_post_status.mjs

draft

schedule

Authentication

references/api-contract.md

• PostPlus backend holds the Postiz API key server-side; scripts never receive it directly
• all Postiz API calls are proxied through the hosted capability bridge
• do not ask users for Postiz credentials of any kind

Default workflow

1. User requests channel onboarding via the product UI or CLI.
2. Product generates an invite link for the target platform.
3. User authorizes their social account via the platform OAuth screen.
4. Product labels the new channel integration with the user's account id.
5. List integrations to confirm the exact integration id for the user's channel.
6. Build the local request JSON.
7. Run

   create_post.mjs

   without

   --execute

   to produce an approval artifact.
8. After approval, re-run

   create_post.mjs --execute --approval-file ...

   .
9. If the post should stay reviewable, keep it in

   draft

   .
10. Only after a second approval, run

    change_post_status.mjs --status schedule

    to queue it for publishing.

Main scripts

• scripts/list_integrations.mjs

• scripts/integration_settings.mjs

• scripts/trigger_tool.mjs

• scripts/upload_media_from_url.mjs

• scripts/upload_file.mjs

• scripts/create_post.mjs

• scripts/change_post_status.mjs

• scripts/list_posts.mjs

• scripts/delete_post.mjs

• scripts/delete_post_group.mjs

• scripts/get_missing_content.mjs

• scripts/update_release_id.mjs

• scripts/platform_analytics.mjs

• scripts/post_analytics.mjs

• scripts/list_notifications.mjs

• scripts/render_publish_report.mjs

Command examples

node skills/50-publishing/social-media-publisher/scripts/create_post.mjs \
  --request "<request.json>" \
  --customer-config "<postiz.config.json>" \
  --output "<create-post.preview.json>"

node skills/50-publishing/social-media-publisher/scripts/create_post.mjs \
  --request "<request.json>" \
  --customer-config "<postiz.config.json>" \
  --output "<create-post.result.json>" \
  --execute \
  --approval-file "<approval.json>"

node skills/50-publishing/social-media-publisher/scripts/change_post_status.mjs \
  --post-id "<post-id>" \
  --status schedule \
  --output "<status.result.json>" \
  --execute \
  --approval-file "<approval.json>"