What Alert and Notification Options Does Feed Control Offer?

Feed Control can notify you through four channels: email, Slack, Discord, and webhooks. Email alerts can be batched into daily, weekly, or monthly summaries, while webhooks deliver each new item individually with a choice of three payload formats: the original HTML, a stripped-down sanitized version, or plain text. These options apply to any feed or monitored web page you set up in the service.

Notification Channels at a Glance

How Each Option Works

Email alerts and summaries

Feed Control sends email alerts when new items are detected. You can also switch to summaries delivered daily, weekly, or monthly. The summary cadence is the main lever for controlling noise: a busy feed that would flood an inbox can be reduced to one digest per week, while a low-traffic page can stay on immediate alerts.

Slack and Discord notifications

Both chat channels receive a notification whenever a new item appears. This fits workflows where the content is acted on by a group rather than an individual — for example, a team channel that watches a competitor's news page or a regulatory update feed.

Webhooks with three payload formats

Webhooks fire once per new item and let you choose what the receiving system gets:

• Original HTML — the content as it appeared, useful when you want to preserve formatting or embedded elements.
• Sanitized version — a stripped-down HTML version, a safer default when the content will be rendered on another site.
• Plain text — the simplest option for search indexing, logging, or messaging systems that don't handle markup.

Because each item triggers its own request, webhooks suit pipelines that need every item rather than a periodic rollup.

Choosing the Right Combination

A practical way to decide:

1. Individual, low-volume monitoring — email alerts, or a weekly summary if the feed is chatty.
2. Shared awareness in a team — Slack or Discord, so new items land where discussion already happens.
3. Feeding another system — webhooks, with the sanitized or plain-text payload unless you specifically need original HTML.
4. Mixed needs — the channels are not mutually exclusive; you can route the same monitored source to a chat channel for visibility and a webhook for processing.

A Concrete Example

Suppose you monitor a government announcements page that publishes a few times a month, and a industry news feed that publishes dozens of items a day. You could send the announcements page to email alerts so nothing is missed, and route the news feed to a weekly email summary plus a webhook into your internal dashboard using the sanitized HTML payload. The result is one inbox that stays quiet and one system that always has the latest items.

Points to Verify Before Relying on It

• Summary timing — the page confirms daily, weekly, and monthly frequencies but does not state the exact send time; check your first summary to confirm when it arrives.
• Webhook payload selection — confirm which format your receiving endpoint expects before enabling it; switching later means reprocessing items already delivered.
• Plan limits — the site links to a pricing page, but the available material does not specify which channels or frequencies are included at each tier. Check the pricing page before building a workflow around a specific channel.

To get started, create the feed or page monitor first, then enable the notification channel that matches the table above.