Skip to main content

Prepare a private draft and verify delivery

See the documented workflow for accounts, preflight, live publication and destination receipts.

Watch on YouTube · Open the video guide

Social Media Automation

Social Media Automation: account setup to verified publication

Connect supported social accounts, prepare private drafts and media, publish deliberately and verify every provider receipt.

Reviewed 13 November 20262 minute read5 steps

Where to start
Marketing → Social Media Marketing Automation

Fields and options

Access needed
View module; separate Manage connections, Create posts, Publish posts and administrator settings
Supported destinations
Facebook Pages, Page-linked professional Instagram, Threads, LinkedIn member profiles, TikTok creators, Pinterest boards, YouTube channels, Bluesky and public HTTPS Mastodon instances.
Content workflow
Own private drafts, own encrypted media library, account-specific captions, live local preview, compatibility preflight and immutable queued publication requests.
Operations
Connection verification, batch health checks, supported token renewal, disconnect, automatic dispatch, asynchronous reconciliation and destination-level receipts.

Before you begin

Start with dedicated test accounts. A configured app, a connected account, an accepted queue request and a verified provider publication are separate milestones.

Follow these steps

  1. Assign the required permissions, then configure the provider apps with the exact callback shown in the selected workspace.
  2. Complete official consent or the supported Bluesky/Mastodon connection flow, choose destinations explicitly and verify their identities.
  3. Prepare a private draft with suitable media, a clear caption, hashtags, link and accessible description. Inspect each destination variation and preview.
  4. Complete network-specific audience, interaction and disclosure controls. Unlock direct publishing only when an authorised controlled test is ready.
  5. Choose Post Now once, inspect each destination receipt and verify the actual content, visibility and final processing in the provider account.

Check the result

Complete the provider-specific first-test procedure and match every destination with the real account outcome. Verify a draft save and connection check caused no external publication.

If something does not look right

Use the OAuth/account-selection guide for callback problems, the media guide for format errors and the receipt recovery guide for uncertain publication. Keep credentials and tokens out of help requests; share redacted request references, destination and UTC time.

Fields, rules and limits

  • Provider app review, organisational ownership, consent, quota and media-domain approval cannot be replaced by the module’s settings.
  • The current UI supports Post Now rather than a future-date social scheduling calendar. It does not publish to X/Twitter, buy ads or generate external AI content.
  • Unknown external outcomes are not automatically replayed. Check the provider before creating a replacement request.

Questions and answers

Can I call a successful queue test end-to-end publishing?

No. End-to-end evidence also needs official consent, correct account identity and direct verification of the actual provider post.

Are all networks ready as soon as the module is activated?

No. Apps, accounts, provider approval, content eligibility and the direct-publishing gate each need separate setup.

Complete task index

Choose the task you need. Each guide includes its screen route, access requirements, steps, result checks and troubleshooting.

Start and configure

Connect accounts

Create content

Publish and verify

Provider guides

Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.