This is an n8n community node that provides webhook-based triggers for Mercury banking events. It lets you automatically start n8n workflows when transactions or account balances change.
n8n is a fair-code licensed workflow automation platform.
Installation | Credentials | Trigger Events | Usage | Architecture | Compatibility | Resources
Follow the installation guide in the n8n community nodes documentation.
- In Mercury, go to Settings > API Tokens.
- Click Create token and give it a name (e.g., "n8n").
- Copy the token — it's only shown once.
- In n8n, go to Credentials > Add Credential and search for Mercury API.
- Paste the token into the API Token field and save.
The Mercury node starts your workflow when one of the following events occurs:
| Trigger Type | Description |
|---|---|
| Transaction Created | A new transaction is created on any account |
| Transaction Settled | A transaction status changes to settled |
| Transaction Failed | A transaction status changes to failed |
| Transaction Cancelled | A transaction status changes to cancelled |
| Transaction Updated | Any update to a transaction (all status and metadata changes) |
| Account Balance Updated | A checking or savings account balance changes |
- In n8n, create a new workflow.
- Add the Mercury node (search for "Mercury" in the nodes panel).
- Select your Mercury API credential.
- Choose a Trigger Type from the dropdown (e.g., "Transaction Created").
- Connect any downstream nodes to process the data (e.g., send a Slack message, update a spreadsheet).
- Activate the workflow.
Once active, the workflow runs automatically whenever the selected event occurs in Mercury. The trigger outputs the full resource — for transaction events, this is the complete transaction object; for balance events, the complete account object.
To stop receiving events, deactivate the workflow. The webhook is cleaned up automatically.
This node uses Mercury's webhook API with automatic lifecycle management:
- Activate workflow — n8n registers a webhook with Mercury for the selected event type.
- Receive event — Mercury sends a webhook notification. The node verifies the HMAC-SHA256 signature, then fetches the full resource (transaction or account) from the Mercury API.
- Deactivate workflow — n8n deregisters the webhook from Mercury.
You don't need to create or manage webhooks manually. The node handles registration and cleanup.
All incoming webhooks are verified using HMAC-SHA256 signatures (Mercury-Signature header). Webhooks with missing, invalid, or expired (>5 minutes) signatures are rejected.
Requires n8n >= 1.60.0.