How-To · · 6 min read
A safer social publishing workflow
Connect a provider, prepare media, request approval, and publish with durable delivery receipts.
Last reviewed:
PostCopilot supports connected publishing for Instagram, LinkedIn, and X. Each connection uses the provider's OAuth flow and stores encrypted tokens server-side.
Before an irreversible publish, the service creates a durable reservation. Recognized requests with the same idempotency key reuse that attempt, reducing duplicate risk. Ambiguous provider outcomes require reconciliation, and errors remain visible rather than being presented as confirmed success.
Use Approvals when another person should review a draft. Approval history records who submitted and decided, but publishing remains a separate explicit action.
Frequently asked questions
How does PostCopilot reduce duplicate-post risk?
Before an irreversible publish, the service creates a durable reservation. Recognized requests with the same idempotency key reuse that attempt. This reduces duplicate risk, while ambiguous provider outcomes require reconciliation before retrying.
What happens when a provider returns an error?
The post remains visibly failed or reconciliation-required rather than being presented as confirmed success. Reconcile ambiguous outcomes before retrying; a stored provider receipt is evidence of a successful delivery.
How are account connections secured?
Each connection uses the provider's official OAuth flow — Instagram, LinkedIn, or X — and stores encrypted tokens server-side. Connections are revocable, and a missing connection blocks delivery visibly.
Where do approvals fit in the workflow?
Use Approvals when another person should review a draft. Approval history records who submitted and who decided, and publishing remains a separate explicit action after approval.