Skip to main content

Publish social content

The Publish pillar moves approved creative live. Composer drafts posts; Calendar and Scheduled Posts plan timing; Publish Queue, Failed Publishes, and Published track execution.

Video

Video coming soon for this topic

Who can do this​

Publishers; composers may be separate from approvers.

Before you begin​

  • Networks connected in Integrations
  • Assets available from Ideate and Studio
  • Hashtag sets optional in Hashtags

What you'll accomplish​

  • Post scheduled or published to selected networks
  • Queue monitoring habit established

Step-by-step procedure​

Compose​

  1. Composer (/social/publish/compose).
  2. Select networks (IG, FB, LinkedIn, etc.).
  3. Attach creative from Assets or upload.
  4. Add copy, link, alt text per network tabs.
  5. Save Drafts or pick schedule datetime.

Schedule & calendar​

  1. Calendar (/social/publish/calendar)—drag posts to slots.
  2. Scheduled Posts list—bulk shift during campaigns.
  3. Confirm timezone matches workspace default.

Monitor execution​

  1. Publish Queue—in-flight jobs.
  2. Failed Publishes—retry after fixing auth or media.
  3. Published—permalink archive for reporting.

Hashtags​

Use Hashtags library for consistent tagging across series.

Extended guidance​

Failed Publishes often cluster after API changes—batch retry only after fixing root auth. Keep a shadow calendar in Plans when Scheduled Posts slip so stakeholders see revised dates. UTM parameters in Composer links help Campaign Performance attribute traffic.

Practice scenarios​

Force one controlled failure (expired token), fix via Integrations, retry from Failed Publishes.

Sandbox validation​

Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.

Team rollout checklist​

Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.

Keep learning​

Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.

Verify your work​

  • Post appears on network or Scheduled Posts
  • Published entry includes timestamp and networks
  • Failures cleared after retry

Tips​

tip

Schedule evergreen posts via Calendar in batches monthly—reduces daily Composer load.

important

Each network tab in Composer may enforce different character/media rules—validate all before queue.

Troubleshooting​

| Stuck in queue | Network rate limit; wait and refresh | | Media rejected | Re-export from In Studio at correct ratio | | Wrong account posted | Re-select profile in Composer network picker |

See also​