Configure
Integrations
Connect Email, Slack, Teams, Telegram, Discord, and Webhook destinations.
Overview
Integrations deliver CronFox events to the channels your team already uses. Configure them once under Integrations; they are account-level destinations, not per-task bindings.
Important behavior
- CronFox sends applicable events to every enabled integration.
- Turning on Slack and Discord means both can receive the same failure alert.
- Which events fire (failure, success, DMS missed, digests, and so on) is controlled in Notifications.
Do not expect a “bind this Slack channel to this one task” setting. Enable destinations globally, then filter with notification preferences.
Step-by-step
- Open Integrations in the sidebar (
/integrations). - Choose a type to add (Email, Slack, Teams, Telegram, Discord, or Webhook).
- Fill in the fields for that type (webhook URL, bot token, channel, recipients, and so on).
- Save the integration.
- Use Test in the configure sheet to confirm delivery.
- Leave the integration enabled.
A default Email integration is created when you sign up. Add chat or webhook destinations as needed.
Destination types
| Type | Typical use |
|---|---|
| Inbox alerts and digests | |
| Slack | Channel notifications |
| Microsoft Teams | Team channel webhooks |
| Telegram | Bot messages |
| Discord | Channel webhooks |
| Webhook | Custom HTTP endpoints / automation tools |
Zapier is not a first-class type — use Webhook with your Zapier catch URL if needed.
Test and toggle
- Open the integration from Integrations (configure / edit query params open the sheet).
- Click Test to send a sample payload.
- Disable a destination to mute it without deleting credentials.
- Delete only when you are sure you will not need it again.
Plan limits
Starter allows a small number of integrations (Email + one additional). Pro and Max allow unlimited destinations. See Plans and limits.