QuickAlerts currently supports webhook URL destinations for QuickAlerts notifications, with additional destinations, like Slack, email, SMS, Discord, Pagerduty, and more, coming soon. You can let us know what kind of destination you are interested by sharing feedback.
Webhook Alert Payload
When your QuickAlerts expression finds a match against streaming blockchain data, we send a payload to your destination, instantly.
Webhooks destinations support several different response formats:
- Block data for the block where your expression found a match (EVM and UTXO): This option includes data about the entire block where your QuickAlerts expression found a match, such as the block number, block hash, parent block hash, and other block-level data. This can be useful if you want to analyze the context of the event that triggered the notification and understand what other transactions occurred in the same block.
- All Transactions from the block where your expression found a match (EVM and UTXO): This option includes all transactions that occurred in the block where your QuickAlerts expression found a match. This can be useful if you want to see all the transactions that occurred in the same block as the event that triggered the notification.
- All Transaction Receipts from the block where your expression found a match (EVM - Note: On UTXO this payload will contain All Transactions): This option includes the transaction receipts for all transactions that occurred in the block where your QuickAlerts expression found a match. Transaction receipts contain information about the success or failure of a transaction, as well as gas used and other metadata. On the EVM, transaction receipts are separate from the transactions themselves, while on UTXO chains, this payload will contain all transactions.
- Matching Transactions targeted by your expression (EVM and UTXO): This option includes only the transactions that triggered your QuickAlerts expression, meaning that they match the criteria you specified in your expression. This can be useful if you only care about specific transactions or events that match certain criteria.
- Matching Transaction Receipts targeted by your expression (EVM - Note: On UTXO this payload will contain Matching Transactions): This option includes the transaction receipts for only the transactions that triggered your QuickAlerts expression. Transaction receipts contain information about the success or failure of a transaction, as well as gas used and other metadata. On EVM chains, this payload will only contain receipts for the matching transactions, while on UTXO chains, it will contain only the matching transactions.
- Matching Transaction Hashes targeted by your expression (EVM and UTXO): This option includes only the transaction hashes for the transactions that triggered your QuickAlerts expression, meaning that they match the criteria you specified in your expression. This can be useful if you only care about identifying specific transactions that match certain criteria and don't need any other metadata about the transactions themselves.
- Matching Transactions and Receipts targeted by your expression (EVM): This option includes transactions and transaction receipts for the transactions that triggered your QuickAlerts expression.