Alert Channels

Alert channels are the destinations Fluxtab uses when spend crosses your threshold tiers or when a day spikes above your recent average. You can keep several active; each alert fans out to every active channel.

Supported types: Email, Slack (incoming webhook), Discord, Teams, and a generic webhook URL.

Why use it

Threshold and anomaly checks are only useful if someone sees them. Channels let you put warnings where the team already works — Slack for ops, email for a backup, Discord for a smaller crew — without checking the dashboard every day.

Setup

1. Open Settings → Alert channels.
2. Choose a channel type and paste the destination (email address or webhook URL).
3. Save the channel. Leave it active so deliveries run.
4. Confirm Settings → Alerts has a monthly threshold set and anomaly alerts enabled if you want spike detection.
5. Optionally send a test alert from the channel row.

Slack

Use a Slack Incoming Webhook URL (https://hooks.slack.com/services/…). Create one in your Slack app or workspace webhook settings, then paste it as the channel destination.

For /fluxtab spend in Slack (a different feature), see Slack & Discord bots.

Discord

Use a Discord channel webhook: Server settings → Integrations → Webhooks → New Webhook. The URL looks like https://discord.com/api/webhooks/….

For /fluxtab spend in Discord, see Slack & Discord bots.

Teams

Use an incoming webhook URL from your Microsoft Teams channel connector / workflow. Paste the full HTTPS URL as the channel destination.

Email

Enter an inbox you check. Fluxtab sends alerts to that address via Resend — no webhook URL required for email channels.

How alerts behave

• Threshold — one monthly threshold; warnings at 50%, 80%, 100%, and 120%, deduped per tier for the billing cycle.
• Anomaly — flags a day that spikes well above your recent average (once per day when it fires).

Connected keys stay read-only. Alerts do not stop billing or reject provider requests — they are early warning only.