Skip to main content
This page covers the settings that control how Blnk sends outbound notifications to Slack and to your own HTTP endpoints.

​
Webhook 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.
If using .env, set BLNK_WEBHOOK_HEADERS to a JSON-encoded object. For blnk.json, set notification.webhook.headers to a JSON object.

​
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.

​
BLNK_WEBHOOK_HEADERS

Optional extra HTTP headers Blnk sends with each global webhook request. Use this for authentication tokens, custom Content-Type values, or other gateway requirements. These headers are separate from Blnk’s signing headers (X-Blnk-Signature and X-Blnk-Timestamp). See Webhook security for signature verification.

​
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.