You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -387,6 +387,29 @@ sources:
387
387
```
388
388
389
389
You can add or remove profiles from the connection.yml fileas needed. You can also configure only one or two data sources if you don't need to scan all of them.
390
+
391
+
## Slack Bot Mentions and Workflow Integration
392
+
393
+
Hawk-eye now supports customizable Slack mentions in alert messages, allowing you to trigger internal Slack bot workflows (such as archiving the channel, etc) automatically.
394
+
395
+
### How to Configure Slack Mentions
396
+
397
+
In your `connection.yml`, under the `notify.slack` section, add a `mention` key. This value should be the Slack user ID of your bot in the format`<@USERID>`. Using the display name (e.g., `@DataScanBot`) will not trigger a real mention—Slack requires the user IDformat.
398
+
399
+
**Example:**
400
+
```yaml
401
+
notify:
402
+
slack:
403
+
webhook_url: https://hooks.slack.com/services/...
404
+
mention: "<@U12345678>"# Replace with your bot's actual user ID
405
+
```
406
+
407
+
When Hawk-eye sends a Slack alert, the message will begin with this mention, ensuring your bot is properly notified andany associated workflows are triggered.
408
+
409
+
**Tip:** To find your bot's user ID, click on the bot's profile in Slack and look for the IDin the URL (e.g., `/team/U12345678`).
0 commit comments