Channels — deliver, and publish.
One page, two jobs: where your daily brief lands, and where your finished articles ship. Slack, Telegram and Discord for delivery; WordPress for publishing.
The Channels page answers two different questions that happen to live on the same screen: where does my morning brief arrive, and where do my finished articles get published. They're independent — you can run either without the other.
Two halves, two jobs
- Delivery (top) — the brief, the drafted posts and the blog angle, pushed to a chat app every morning. Slack, Telegram or Discord.
- Publish (bottom) — a finished BlogCraft article, pushed to your website. WordPress.
Both are set per brand. Switch brand and you're configuring that brand's channels, not your account's.
Delivery — where your brief lands
Three channels can be added today:
On Free the brief stays in the dashboard and the Add-channel button is locked — none of the three can be connected. Starter includes one channel; Pro and Agency are unlimited. See plans →
| Channel | How it connects | Verified when |
|---|---|---|
| Slack (recommended) | One click — approve on Slack's screen and pick a channel. Guide → | Immediately on save. |
| Telegram | No IDs to copy. Add it, tap Connect Telegram, press Start in the bot. Guide → | The bot links your chat. |
| Discord | One click — authorize on Discord's screen and pick a server + channel. Guide → | Immediately on save. |
A webhook URL is the credential, so pasting a valid-looking one marks the channel verified on the spot. Nothing calls it to check. A typo'd or long-since-deleted webhook will sit there showing green while every brief silently fails. Always hit Test. This only applies if you paste a webhook by hand — connecting Slack or Discord in one click gets the webhook from them directly, so it can't be mistyped. Test sends →
You can connect more than one at a time — the brief goes to all of them, at the same moment. That moment is one schedule per brand, which surprises people often enough that it has its own page.
Email and WhatsApp are retired
They were channels once, and you may still see them in older screenshots. They are gone now — the brief is delivered to Slack, Telegram and Discord.
- You can't add an email or WhatsApp channel. The picker doesn't offer them, and the app refuses if you try.
- Any old rows have been removed. If you had one, it is no longer listed, and it was not delivering — email delivery stopped working in June 2026 and WhatsApp was never switched on.
If your brief has to reach an inbox, the usual answer is Slack or Discord in a channel that emails its members — or Telegram on the phone, which is what most people end up preferring anyway.
What a channel row gives you
Each channel shows its status badge — Verified when it can receive, Pending while you finish connecting it, Paused if you paused it, or Disconnected if the app or webhook was removed on the other end — its target — webhook URLs are masked, on purpose — and the hour and timezone it's set to. Then four controls:
- Test — fires a sample brief right now. What it sends →
- Pause / Resume — stop delivery without losing the channel or its history.
- Delete — remove the channel.
- There is no Edit. To change the hour, the timezone or a webhook URL, delete the channel and add it again. Why →
Under the list sits Delivery history — your last 20 sends, and the only place a failed delivery is ever reported.
Publish — where your articles ship
WordPress is the only publishing destination today. Type your site address, click Connect WordPress, and approve ScoutRival on your own site — no plugin to install, nothing to copy. Full setup →
One connection-level setting decides what happens to a finished article:
- Draft only — the article is saved to WordPress as a draft. You press publish there.
- Queue for review — the article waits in ScoutRival until you approve it, then goes out.
- Auto-publish — it goes live the moment it's finished.
The Post a test button on the WordPress card creates a live post on your blog — even when the mode is set to Draft only. It is a genuine publish, not a dry run. Expect it to appear on your site, and delete it afterwards.
No channel, no brief
Worth stating plainly, because it's the single most common support question:
A brand with no connected delivery channel does not get a brief generated at all. Not generated-but-undelivered — not generated. We don't spend your credits writing something nobody asked to receive. A paused channel doesn't count as connected either.
Connect one channel, hit Test, and the mornings take care of themselves. More on delivery →