loading
loading
Utilities
Publish tool output to chat and alerting providers.
overview
notify is the delivery stage after a scanner finishes. It takes another tool's output and posts it to a configured provider.
Set -provider and -id to route workflows to different channels. Use -bulk and -delay when a noisy run would flood a room.
Trickest runs notify as a managed Utilities node. Wire -data from an upstream FILE; the node writes a record of what was sent.
use cases
Send a scanner's output straight to a chat channel so the team sees a fresh CVE or exposure as a message instead of a buried file.
Use bulk mode to batch a results file into a compact summary rather than a stream, posting one digest at the end of a workflow.
Set the provider and id so different workflows post to different destinations, keeping recon noise and critical alerts apart.
Set a character limit and a rate limit so long output splits cleanly and a high-volume run does not flood or get throttled.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| id | STRING | -id | id to send the notification to (optional) |
| bulk | BOOLEAN | -bulk | enable bulk processing |
| data | FILE | -data | input file to send for notify |
| delay | STRING | -delay | delay in seconds between each notification |
| proxy | STRING | -proxy | http proxy to use with notify |
| silent | BOOLEAN | -silent | Don't print the banner |
| verbose | BOOLEAN | -v | enable verbose mode |
Showing key inputs. notify exposes 13 inputs in total.
| Name | Type | Flag | Description |
|---|---|---|---|
| id | STRING | -id | id to send the notification to (optional) |
| bulk | BOOLEAN | -bulk | enable bulk processing |
| data | FILE | -data | input file to send for notify |
| delay | STRING | -delay | delay in seconds between each notification |
| proxy | STRING | -proxy | http proxy to use with notify |
| silent | BOOLEAN | -silent | Don't print the banner |
| verbose | BOOLEAN | -v | enable verbose mode |
| provider | STRING | -provider | provider to send the notification to (optional) |
| char-limit | STRING | -char-limit | max character limit per message (default 4000) |
| msg-format | STRING | -msg-format | add custom formatting to message |
| rate-limit | STRING | -rate-limit | maximum number of HTTP requests to send per second |
| config-file | FILE | -config | notify configuration file |
| provider-config-file | FILE | -provider-config | provider config file |
example
# notify: send findings to the configured Slack providercat findings.txt | notify -provider slack -bulk -delay 1[notify] provider=slack[notify] sent 12 lines in bulk[notify] channel=#recon-alerts[notify] status=ok[notify] doneguidance
Use notify at the end of a workflow when findings should land in chat or email. It does not scan or discover; it delivers another tool's output. Prefer json2html or generate-yaml-report when you need a file report instead of a live alert.
Renders findings as an HTML report instead of pushing them to chat. Pick by whether you want a file or a live alert.
Builds a structured report from results. notify is for delivery to a platform rather than report formatting.
Captures output to a file for the workflow. notify takes that file and publishes it onward.
faq
related
Spider a URL and return a wordlist for password crackers.
Wordlist and mined-word subdomain permutation.
Import, export, and upsert workflow data against an Airtable base.
Decode Android APK files into smali sources and resources.
Check a file's values against conditions and exit with a matching code.
Authenticated Route53 hosted-zone inventory.
Targets are scanned by nuclei, then notify streams the findings to a chat platform and writes a record of what was sent as a queryable output.
Facts on this page come from the live Trickest tool library.