Notification Connections
KeeperHub supports multiple notification channels. Configure connections to enable notification nodes in your workflows.
Accessing Connections
- Click your profile icon in the top-right corner
- Select Connections
- View existing connections or add new ones
Available Connection Types
Send notifications directly to email addresses.
Setup:
- Click Add Connection and select Email
- Configure your email provider settings
- Save the connection
Features:
- Direct delivery to specified addresses
- Customizable subject and message content
- Support for dynamic variables from workflow
Discord
Send messages to Discord channels via webhooks.
Setup:
- In Discord, go to Server Settings > Integrations > Webhooks
- Create a new webhook and copy the URL
- In KeeperHub, add a Discord connection with the webhook URL
Features:
- Channel-specific message posting
- Rich message formatting
- Real-time delivery
Slack
Connect to Slack workspaces for team notifications.
Setup:
- Click Add Connection and select Slack
- Authorize KeeperHub to access your Slack workspace
- Select default channel (can be changed per node)
Features:
- Workspace and channel targeting
- Thread support for organized conversations
- Mention capabilities for urgent alerts
Telegram
Send messages to Telegram chats and channels via bot API.
Setup:
- Create a Telegram bot using BotFatherÂ
- Copy the bot token provided by BotFather
- In KeeperHub, click Add Connection and select Telegram
- Paste your bot token and save
Features:
- Send messages to any chat, group, or channel
- Support for plain text and MarkdownV2 formatting
- Dynamic variables from workflow data
Configuration Fields:
| Field | Description |
|---|---|
| Chat ID | Numeric chat ID or @channelusername |
| Message | Message content (supports dynamic variables) |
| Parse Mode | Plain text or MarkdownV2 |
MarkdownV2 Note: When using MarkdownV2 parse mode, special characters (., -, _, *, [, ], (, ), ~, `, >, #, +, =, |, {, }, !) must be escaped with a backslash (\).
Webhook
Send HTTP requests to any external service.
Setup:
- Click Add Connection and select Webhook
- Configure:
- URL: Must begin with https://
- Method: GET, POST, PUT, etc.
- Headers: Authentication and content-type headers
Features:
- Integration with any HTTP-compatible service
- Custom JSON payloads
- Dynamic variables in request body
Using Connections in Workflows
After setting up connections, use them in notification nodes:
- Add a notification node to your workflow (Send Email, Send Discord Message, etc.)
- Click the node to open configuration
- Select your connection from the Connection dropdown
- Configure the message content
Connection Status
The configuration panel shows connection status:
- Green checkmark: Connection is valid and ready
- Red indicator: Connection needs attention (expired, invalid credentials, etc.)
Dynamic Variables in Messages
Include workflow data in your notifications using variables:
| Variable | Description |
|---|---|
${balance} | Balance value from Check Balance node |
${address} | Wallet or contract address |
${network} | Blockchain network name |
${timestamp} | Execution timestamp |
${workflow_name} | Name of the workflow |
${node_name} | Name of the triggering node |
Example Discord Message:
Balance Alert: Wallet ${address} on ${network} now has ${balance} ETHBest Practices
Redundancy
Configure multiple notification channels for critical workflows. If one channel fails, others will still deliver.
Testing
Test your connections after setup using a simple workflow with a manual trigger.
Security
- Use HTTPS for all webhook URLs
- Avoid including sensitive data (private keys, passwords) in notification messages
- Regularly review and rotate webhook URLs if compromised
Channel Organization
- Use dedicated Discord/Slack channels for KeeperHub alerts
- Consider separate channels for different workflow types (alerts, transactions, monitoring)