Slack alerts deliver Parsivex notifications directly to a channel your team already watches. Slack is available on the Team plan only. Monthly Monitoring subscribers receive email alerts but cannot configure Slack.
What Slack receives
Once connected, your webhook receives two kinds of messages:
| Alert type | When it fires | Learn more |
|---|---|---|
| Monitoring | After a successful monthly re-scan finds new waste or resolved findings | Email and Slack monitoring alerts |
| Cost anomaly | Daily, when yesterday's spend spikes above baseline (if anomaly alerts are enabled) | Cost anomaly alerts |
Both use the same webhook URL configured in Integrations → Alert channels.
Prerequisites
- A Team plan subscription with an active or trialing status
- Permission to create an Incoming Webhook in your Slack workspace
- A target channel where the team should see Parsivex alerts
Configure the webhook
Create a Slack incoming webhook
In Slack, open Apps → Incoming WebHooks (or create a Slack app with an Incoming Webhooks feature). Choose the channel for Parsivex alerts and copy the webhook URL. It looks like:
https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXXPaste the URL in Parsivex
Go to Integrations (
/integrations) and open Alert channels. Under Slack alerts, paste the webhook URL into the input field and click Save.Parsivex verifies the URL by posting a test message:
Parsivex connected successfully.If verification fails, double-check the URL and that the Slack app is still installed.Confirm delivery
After saving, you should see the test message in your Slack channel. Future monitoring and anomaly alerts will post there automatically.
The settings page shows a masked version of your connected URL (last eight characters visible) so you can confirm which webhook is active.
What messages look like
Monitoring alert (after a re-scan)
When new waste is found:
🔍 $120/month in new AWS waste detected — 2 new finding(s)
The message may also include:
- A resolutions line when findings were fixed:
✅ 3 findings fixed — $85/month saved since last scan - The top new finding:
Top finding: Idle EC2 instance — $85/mo - A View Report button linking to your Parsivex report
When no new waste appears:
✅ No new AWS waste found this month.
Cost anomaly alert (daily)
When daily spend spikes are detected, Slack receives a batched message listing each affected service, baseline vs actual amounts, and severity. Multiple services on the same day are combined into one Slack message, not one per service.
Disconnect Slack
To stop Slack delivery, click Disconnect in Integrations → Alert channels. Parsivex clears the stored webhook URL. Email alerts continue unchanged if your plan includes them.
Troubleshooting
| Problem | What to try |
|---|---|
| "Requires Team Plan" when saving | Upgrade to Team from Billing (/settings/billing) or the pricing page |
| "Could not verify webhook URL" | Confirm the URL is complete, the Slack app is installed, and the channel still exists |
| No Slack messages after connecting | Monitoring alerts only fire on follow-up scans; anomaly alerts require anomaly alerts enabled and a paid plan |
| Messages stopped suddenly | The webhook may have been revoked in Slack — create a new one and update Integrations |
Related topics
- Email and Slack monitoring alerts — when monitoring messages are sent and what they include
- Cost anomaly alerts — daily spike detection and the workspace toggle
- Plan comparison — Team plan features and limits