This page covers the settings that control how Blnk sends outbound notifications to Slack and to your own HTTP endpoints.
Notification settings
Use the notification object to configure Slack incoming webhooks and a generic application webhook. You can set either integration alone, or both at the same time.
BLNK_SLACK_WEBHOOK_URL=
BLNK_WEBHOOK_URL=
BLNK_WEBHOOK_HEADERS={}
| Description | Default |
|---|
BLNK_SLACK_WEBHOOK_URL | Slack incoming webhook URL used for team alerts. | None |
BLNK_WEBHOOK_URL | HTTPS endpoint that receives Blnk event notifications. | None |
BLNK_WEBHOOK_HEADERS | JSON object of extra HTTP headers sent with webhook requests (for example authentication). | {} |
BLNK_SLACK_WEBHOOK_URL
When set, Blnk can post messages to the Slack channel associated with the incoming webhook.
To create a webhook URL, follow Slack’s guide: Sending messages using incoming webhooks.
Treat Slack webhook URLs like secrets. Anyone with the URL can post to your channel, so store them in a secret manager or environment variables, not in version control.
BLNK_WEBHOOK_URL
When set, Blnk delivers notifications to your application at this URL. Use this when you want to trigger workflows, sync internal services, or custom alerting outside of your ledger.
Need help?
We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool.
To ask questions or discuss issues, please contact us or join our Discord community.
Tip: Connect to Blnk Cloud to see your Core data.You can view your transactions, manage identities, create custom reports, invite other team members to collaborate, and perform operations on your Core — all in one dashboard.Check out Blnk Cloud → 
