Webhook
Overview
The Webhook allows you to execute workflows remotely from external sources. Instead of triggering actions manually, or on some set precise time, you can now run workflows real-time in response to or reaction to certain external events.
This is ideal for automation use cases such as monitoring user cases, for real-time interactions based on certain other external triggers.
What the Webhook Do
The Webhook acts as a event-based trigger that starts your workflow execution in reaction to any external event. Once configured, it runs independently without manual intervention.
The webhook is configured so that no duplicate requests can be made within 2 seconds. This is to ensure duplicate requests are not made out in error, and to ensure any DDOS attacks.
Hence, please make sure to wait 2 seconds before making a 2nd request; else it will return a failed message.
The webhook comes some few key security capabilities:
None: Quick and easy setup with an open access; perfect for the public-facing utilities. Anyone with access to the given link or by clicking the link (either from a form or button) will directly trigger the workflow.
Basic Auth: A basic way to keep your things private with a user defined username and password. This is a basic
JWT Token: Enterprise grade security best suited for enterprises.
Configuration Options
1. Security
Choose your desired security level from any of the following options:
None
Basic Auth (Username/Password)
JWT Tokens (Enterprise grade security)
2. Create Webhook link
By clicking the set button, it generates a unique webhook URL link:
This URL is very unique and specific to your given workflow only.
You have the provision to reset it anytime you feel that the link has been compromised or exposed.
3. Trigger
You can now go ahead and copy-paste that generated webhook URL to your destination locaiton.
Example:
Web browser
3rd party applications (Zapier, Make.com, n8n etc)
Postman
Common Use Cases
Event monitoring
Delayed smart contract execution
Automated periodic fund transfers
Scheduled data reads or API calls
Time-based notifications or alerts
Example Workflow
Scenario: Run a Web3 workflow when a n8n has completed certain process.
Webhook:
URLWhen to Run:
n8n API call node is executed
Result: The Web3 workflow executes automatically every time the API node in n8n is executed.
Last updated