Slack integration
Get Maskflare alerts in Slack
- Request blocked, File blocked, Malicious file and Block spike
- Policy change proposed and Policy change decided, so approvers see requests for a second pair of eyes
- Device unprotected, API key expiring, Invitation pending and Issue reported
- Config changed, API key created and the Weekly digest
Some events need a person to look at them quickly: a spike in blocked requests, a policy change waiting for a second approver, a device that has been unprotected for an hour. A Slack channel is where those people already are.
Maskflare has a Slack destination type. Add an incoming webhook URL, choose the events, and each one arrives as a short message with a link to open it in the console.
What it does
- Request blocked, File blocked, Malicious file and Block spike
- Policy change proposed and Policy change decided, so approvers see requests for a second pair of eyes
- Device unprotected, API key expiring, Invitation pending and Issue reported
- Config changed, API key created and the Weekly digest
Set up Slack with Maskflare
Maskflare posts a message to a Slack channel through an incoming webhook URL. Messages show a fixed set of metadata fields and a link back to the console.
- In Slack, create an app (or reuse one), open Incoming Webhooks and switch on Activate Incoming Webhooks.
- Select Add New Webhook to Workspace, choose the channel and select Authorize. For a private channel, you must be a member of it first. Copy the webhook URL.
- In the Maskflare console, open Connections, then Integrations and select Add endpoint.
- Set Destination to Slack and paste the webhook URL into URL. Add a Description such as the channel name.
- Under Events, tick the events to send. Request processed is not available for Slack, because a message per request would bury the channel.
- Select Add endpoint, then Done. Select Send test event on the endpoint row to check the message arrives.
What data is shared
- Each message shows the event title, your organization, and a fixed list of fields when they apply: environment, provider, model, mode, outcome, status code, reason, rule key, counts and similar identifiers.
- Messages include a link that opens the matching page in the Maskflare console.
- Never sent: prompts, responses, file names or contents, detected values, the free-text description of an issue report, a person's email address or the details of a configuration change.
- Anyone who can see the Slack channel can see these fields, so choose the channel with that in mind.
Good to know
- Treat the webhook URL as a secret: anyone who has it can post to the channel. Maskflare stores the URL with the endpoint and never writes it to its logs.
- Request processed, the per-request event feed, can't be sent to Slack. Use Splunk or an HTTPS endpoint for that.
- Each delivery is retried on failure, up to six attempts in all, and the Deliveries view shows the result of recent attempts.
Vendor documentation
Frequently asked questions
Does Maskflare have a built-in Slack integration?
Yes. Choose Slack as the destination on Connections, Integrations, paste an incoming webhook URL and pick the events.
Will Slack messages contain sensitive data?
No. Messages contain a fixed list of metadata fields and counts, plus a link to the console. Prompts and detected values are never included.
Can I send every request to Slack?
No. Request processed is not available for Slack or PagerDuty, because it produces one event per AI request.
Can I post to several channels?
Yes. Add one endpoint per webhook URL and give each a different set of events.
Other siem and alerting integrations
See it on your own data
Try Maskflare free.
Bring your hardest prompts.
28-day free trial or 10,000 requests, whichever comes first. Point one app at the gateway or enroll a few laptops,
and watch what gets masked. Or talk to us first.
- SOC 2 Type II: In progress
- ISO 27001: In progress
- EU hosting by default · on-premises available
- Prompts and files never stored
- Never used to train AI models
- GDPR · nDSG · DPA available
- Trust center →