Navigation

Login to see more
Help Center

Basics

  • Navigating the app
  • More features

Settings

  • Settings overview

Tasks & board

  • Using the Kanban board
  • Using the Planner

Files

  • Files and formats

Koords (points)

  • All about koordy (points)

Publishing

  • Publishing to external platforms
Back to Help Center

Publishing to external platforms

Publishing lets you write a post once and send it to several external platforms at the same time — the inverse of channel mirrors, which pull content in. Supported destinations: Telegram, WordPress, Discord, Slack, a generic webhook (Zapier / Make / n8n / your own service) and the Meta family — Facebook, Instagram, Threads.

Enabling the feature

Publishing is off by default. To turn it on for a channel, open Channel settings → General tab → "Optional channel features" and switch on Publishing. Only a channel owner or admin can do this, and the feature is not available for direct messages or support channels.

How to open

In a channel you manage (owner/admin, regular channels only), press the Megaphone button in the channel sub-header. If the button is missing, check that the "Publishing" feature is not turned off in the channel settings. The page has three sections: Destinations, Composer and History.

Destinations (connections)

Press "Add destination" and choose a platform — the form shows the fields it needs, and a collapsible "How to set up" block right in the dialog repeats the steps from this article. Before saving, press "Test connection" — the app calls the platform and tells you whether the credentials work. Saved credentials are encrypted at rest and are never returned by the API. Each destination can be toggled on/off or deleted.

Step-by-step platform guides: Telegram · WordPress

Telegram

You'll need: a bot token and the chat id of your channel or group.

  1. Open @BotFather in Telegram, send /newbot and answer the prompts (bot name and @username). BotFather returns an HTTP API token — copy it.
  2. Add the new bot to your channel or group as an Administrator with the "Post messages" right (Channel → Administrators → Add Admin → find the bot by @username).
  3. Find the Chat ID: for a public channel it is its @username (e.g. @my_channel). For a private one, forward any of its posts to @userinfobot and copy the id it shows: numeric, starting with -100.
  4. Paste the token and chat id into the form and press "Test connection".

If it fails: the most common cause is the bot not being an admin of the channel (or having been removed); also check the token was copied in full. Telegram is the only platform that supports the composer's Poll mode.

WordPress

You'll need: the site URL, a username and an application password.

  1. You need WordPress 5.6 or newer, reachable over HTTPS. Log in to the site's admin as the user the posts should be authored by.
  2. Open Users → Profile and scroll to Application Passwords. Enter a name such as "Coordio" and press "Add New". Copy the generated xxxx xxxx xxxx xxxx xxxx xxxx password — it is shown only once. More in the WordPress documentation.
  3. In the form, enter the site root URL (e.g. https://my-site.com), the username and the copied application password. It is not your login password.
  4. Pick the post status: "Publish" makes posts go live immediately; "Draft" saves them on the site for review before publishing.

If it fails: security plugins (Wordfence, iThemes, etc.) may disable the REST API or application passwords — re-enable them in the plugin settings. The Application Passwords section does not appear on sites without HTTPS.

Composer & fan-out

The composer has two modes:

  • Post — write the text once and optionally add image URLs. Each platform receives the image in its own shape (Instagram, for example, gets an automatic 1:1 crop).
  • Poll — ask a question with 2–10 answer options, optionally with multiple answers or named (non-anonymous) voting. Handy for attendance or role sign-ups. Polls go to destinations that support them (Telegram); others are skipped.

Then tick the destinations and either Publish now or Schedule a time (a background job sends it when due). The same content goes to every selected destination.

History & status

Every post appears in History with a status badge per destination — Published (with a link to the live post) or Failed with the reason shown under the badges. A failed leg can be retried or published now. Statuses update live.

What's next

A later phase adds AI rewriting per platform and language, so each destination gets a version tailored to its audience.