Skip to content

Sharing social posts

Your workspace can hold a queue of ready-to-post social content — a caption plus an optional image or video URL — that an automation or an agent drafts, and a person reviews and pushes out through their phone’s native share sheet.

The automation never posts on anyone’s behalf. The person’s tap on the platform’s own Share button (or the explicit “Mark as posted”) is the approval — the same wall the rest of Vroxy keeps.

Three ways, all landing in the same queue:

  • Server-to-server — a workspace API token with tenant:write posts a draft to POST /api/v1/social (see the REST API).
  • A dispatch agent — a code agent drafts a post straight into the queue, and the workspace (or a named person) is nudged.
  • By hand — the Social page in your workspace and the mobile app both have a draft form.

A draft is caption (required) plus optional media_url / media_kind (image or video) and a free-text suggested_destination such as “Instagram reel”.

The person opens the Social section in the mobile app (or the Social page in the workspace) and, for each card, either taps Share to hand the media and caption to the phone’s native share sheet, or taps Mark as posted when they’ve posted it outside the sheet. Either way records who pushed it and where, so the automation that drafted it can see that it’s done.

A draft can also be ignored, or it expires on its own.

Two permissions split the surface:

  • social.read — see the queue. Held by operators and up.
  • social.write — draft, mark shared, mark ignored. Held by members and up.

There’s also a dedicated influencer seat whose entire surface is the share queue — read plus write, and nothing else: no chats, docs, members, rooms or settings. It’s the seat for a social media marketer or influencer who posts to their own page and does no support work. An admin invites them like any other member; the level just appears in the role dropdown.

Every workspace gets a dedicated #social room — the home where an automation or agent drafts share posts and a person reviews them. It’s dispatch-enabled, so a daily nudge posted there wakes the agent without needing an @-mention, and the agent drafts through the API and reports back in the room.