Before you begin
Publisher requires an active trial or Pro entitlement. Writer and Converter remain free. Simulation checks the workflow without sending your article to a platform; it does not prove that a real account has publishing permission.
1. Prepare the article
Choose Publisher, set a title, and review the content copied from your document. A queued job keeps a snapshot. Later edits in Writer do not silently change an already queued article.
2. Choose destinations and delivery modes
Start with one destination. WordPress needs an HTTPS site address, a username, and an Application Password with permission to create posts. Other automatic adapters have their own credentials and account requirements. Assisted destinations open the official platform editor for you to review and submit the content.
LinkedIn and other platforms may restrict API access. An assisted handoff can still be useful when your application lacks that permission. Opening an editor or copying content does not mean a post has been published.
3. Queue and inspect a simulation
Review the title, snapshot, selected destinations, and modes before running the job. Check the outcome for every destination. A successful simulation is a local test, so it will not create a remote draft or public URL.
4. Send and review each result
For a real delivery, configure the account, choose the intended mode, and confirm the external action. Remote-draft adapters create drafts for review. A Webhook recipient may publish publicly as part of its workflow, so inspect that workflow before sending.
Read the status carefully
| Outcome | What to do |
|---|---|
| Simulated | No external delivery took place. Configure a real connection when ready. |
| Draft created | Open the destination and review the draft before publishing. |
| Accepted or processing | The receiver has accepted the request. Check its reported status before treating it as published. |
| Unknown | Check the destination before taking another action; the request may already have succeeded. |
| Failed or cancelled | Read the reason, correct the setup, and retry only the affected destination when allowed. |
Keep the delivery record
Use the publishing history to review per-destination outcomes. Confirm an article on the destination platform before sharing its URL. After a timeout, do not create a duplicate job just to see whether the second one succeeds.
Destination overview · Connect an automation tool · Trial and Pro access