Structured, professional drafts from the workspace Brand Kit — then advisory review, explicit scheduling, and official-API publishing with receipt-backed delivery state.
LinkedIn rewards structure: a hook line, a developed middle, a clear takeaway. PostCopilot's LinkedIn adaptation writes for that shape instead of padding a tweet. Drafts are grounded in your Brand Kit, so recurring themes, vocabulary, and audience framing stay consistent across posts.
Connect LinkedIn once through its official OAuth flow; tokens are encrypted server-side and revocable. Publish immediately or on an explicit schedule — publishing uses durable idempotency reservations to reduce duplicate risk, and ambiguous provider outcomes stay reconciliation-required instead of being reported as confirmed success. delivery receipts are stored, while metrics and engagement can be synchronized on demand where supported.
Comments and replies can be synchronized into the workspace on demand where supported, and Alex (the relationships chat role) can prepare response drafts. Sending a reply is always an explicit confirmed action — drafts never leave the workspace on their own.
Yes — through LinkedIn's official OAuth connection, on your explicit action or configured schedule. Successful delivery stores the provider receipt; ambiguous outcomes remain reconciliation-required instead of being treated as confirmed success.
That is what the workspace Brand Kit is for: identity, voice, audience, and references are defined once and used by supported generation flows.
Yes. Route a draft through an advisory review and record who decided. Publishing remains a separate explicit or scheduled action, and workspace roles control those actions.
Durable idempotency reservations let recognized retries reuse the same attempt and reduce duplicate risk. Ambiguous provider outcomes require reconciliation before retrying.
Draft in your brand voice, approve what matters, and publish with confirmed delivery state.