How the feature works
A third-party service sends a webhook; this request is addressed to the URL that serves as the entry point in Eventmaker. As soon as it is received, the workflow starts.
Selecting the trigger
In the Automation interface, choose the trigger "Webhook is received" as the starting point of the workflow.
2. Generating the URL
After selecting this trigger, a unique URL can be generated. This URL will be provided to the third-party service, which will send its HTTP request to it.
3. Testing reception
A test mode is available: click the "Test" button to open the test window. Copy the test URL, then click "Listen to the webhook URL." During this phase, it is possible to send a GET or POST request to the provided URL in order to analyze the structure of the transmitted data.
4. Data usable in the workflow
Once the test request is received, the data structure is recorded. Subsequent workflow steps can then use this data.
Required Configuration
Set up a third-party service or a script capable of sending a POST or GET request containing data.
💡When an automation with a webhook as its origin is inactive, the request is stored but the workflow does not trigger. Processing can be resumed once the workflow is reactivated.
Conclusion
Receiving a webhook as a trigger opens up new automation possibilities. It enables integration of external solutions with Eventmaker and chaining of custom actions.