Updated Jul 15, 2026

Utilities

Push scanner findings to chat and alert channels

Publish tool output to chat and alerting providers.

Agent

overview

What notify does

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.

source github.com/projectdiscovery/notify

use cases

Where notify fits

Alert on new findings

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.

Publish a run digest

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.

Route to the right channel

Set the provider and id so different workflows post to different destinations, keeping recon noise and critical alerts apart.

Keep messages within platform limits

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

notify inputs and flags

13 inputs
NameTypeFlagDescription
idSTRING-idid to send the notification to (optional)
bulkBOOLEAN-bulkenable bulk processing
dataFILE-datainput file to send for notify
delaySTRING-delaydelay in seconds between each notification
proxySTRING-proxyhttp proxy to use with notify
silentBOOLEAN-silentDon't print the banner
verboseBOOLEAN-venable verbose mode

Showing key inputs. notify exposes 13 inputs in total.

Full flag reference (13 inputs)
NameTypeFlagDescription
idSTRING-idid to send the notification to (optional)
bulkBOOLEAN-bulkenable bulk processing
dataFILE-datainput file to send for notify
delaySTRING-delaydelay in seconds between each notification
proxySTRING-proxyhttp proxy to use with notify
silentBOOLEAN-silentDon't print the banner
verboseBOOLEAN-venable verbose mode
providerSTRING-providerprovider to send the notification to (optional)
char-limitSTRING-char-limitmax character limit per message (default 4000)
msg-formatSTRING-msg-formatadd custom formatting to message
rate-limitSTRING-rate-limitmaximum number of HTTP requests to send per second
config-fileFILE-confignotify configuration file
provider-config-fileFILE-provider-configprovider config file

example

Run notify

notify · command
# notify: send findings to the configured Slack providercat findings.txt | notify -provider slack -bulk -delay 1
sample output
[notify] provider=slack[notify] sent 12 lines in bulk[notify] channel=#recon-alerts[notify] status=ok[notify] done

guidance

Choosing notify

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.

json2html

Renders findings as an HTML report instead of pushing them to chat. Pick by whether you want a file or a live alert.

generate-yaml-report

Builds a structured report from results. notify is for delivery to a platform rather than report formatting.

string-to-file

Captures output to a file for the workflow. notify takes that file and publishes it onward.

faq

notify questions

No. It only delivers the output of other tools or the contents of a file to a platform. Run it as the final stage after discovery and scanning.

Run notify yourself

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.