Social Media Automation · Feature guide

Publish with Post Now and verify every destination receipt

Submit one deliberate request, follow automatic dispatch and confirm the actual network outcome before reporting success.

Audience: authorised staffReviewed 13 November 2026

Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.

Where to start

Create a post → Post Now → receipt; Publishing activity → View destinations

Permission

Create posts + Publish posts; direct gate enabled; eligible connections and content

Before you begin

Use authorised test accounts for the first publication. Review identity, visibility, caption and media for every selected destination before submitting.

Follow these steps

Complete the post and destination-specific controls, then choose Post Now once.
Read the request receipt. The receipt page automatically advances bounded queued work; the normal CRM cron provides a fallback when the browser is closed.
Inspect each destination’s Published, Pending, Failed, Unknown or Skipped result and its reason.
Use a returned remote ID or link where available, then open the provider account and verify the actual post, media and visibility.
Return to Publishing activity to review the saved request and destination history. Investigate uncertain outcomes before creating any replacement request.

Fields and options

Request: A request identifier and payload check protect repeat submission of the same operation; the queued publication content is fixed for that request.
Receipt: Each selected destination has its own outcome. The overall request can be partial when destinations differ.
Provider confirmation: A provider acceptance or upload acknowledgement can precede final processing. A local success page alone is not end-to-end delivery evidence.

Rules and limits

Closing the browser does not cancel an already queued request.
The worker claims work before contacting the network to reduce duplicate dispatch.
Not every provider returns a public permalink; a missing link is not proof of failure.

Check the result

Match each destination receipt with the actual authorised provider account.
Record the request reference, remote ID and verified visibility for the controlled test.

If something does not look right

For Pending, allow provider processing and check the existing receipt.
For Unknown, inspect the provider account before any new submission; the system does not automatically replay an ambiguous external write.

Common questions

Does the receipt prove the post is visible to everyone?

No. Visibility, provider processing and audience restrictions need verification in the actual account.

Can I edit a queued request?

The submitted content is fixed. Prepare a new deliberate draft only after resolving the original outcome.