Docs / Platform
Slack integration
Send Gurdx alerts to a Slack channel using an incoming webhook, with no code to write.
What you need#
- Permission to add apps in your Slack workspace.
- A Gurdx account with the Settings and integrations permission.
Step 1: create an incoming webhook in Slack#
- Open your Slack app directory and create a Slack app (from scratch) for your workspace, for example named "Gurdx alerts".
- Enable Incoming Webhooks for the app.
- Choose Add New Webhook to Workspace and pick the channel that should receive alerts, such as
#fraud-alerts. - Copy the webhook URL. It looks like
https://hooks.slack.com/services/T000/B000/XXXX.
Step 2: add it in Gurdx#
- In
https://gurdx.cretip.com/app, open Settings, then Integrations, and add a new integration of type Slack. - Paste the webhook URL.
- Choose the event types to send, or leave it on all events.
- Set a minimum risk score, for example 60.
- Save and enable it.
Step 3: test it#
Trigger a real event by calling an endpoint with a value that scores high in live mode, such as a known Tor exit IP.
curl "https://gurdx.cretip.com/api/lookup/ip/threats?ip=203.0.113.42&userID=slack-test" \
-H "Authorization: Bearer $GURDX_KEY"
Note: Test mode (
mode=testor agx_test_key) never raises events, so it will not produce a Slack message. Use a live key for the check.
What Slack receives#
Gurdx posts a plain-text message to the webhook as {"text": "..."}:
🛡️ Gurdx — Fraudulent payment attempt (My Shop)
Risk: 91/100
User: user_1042
Time: 2026-10-06 12:14:22
Troubleshooting#
- Nothing arrives: check the integration is enabled, the event type is selected and the minimum risk score is not above the event's score.
- Slack answers an error: the webhook URL was revoked or the app was removed from the channel. Create a new webhook and update the integration.
- Too noisy: raise the minimum risk score or limit the event types.
Failed sends are retried up to 3 times, one minute apart. For richer formatting or buttons, receive a webhook and post to Slack from your own code.
Found a mistake? Tell us on the contact page. Contact