Receiving and sending events

Metaventus moves events through its automation scenarios, in both directions: a scenario can call your system when something happens, and your system can start a scenario by calling Metaventus.

There is no subscription to create through the API: a scenario is composed in the application, then runs on its own.

Metaventus calls your system

The HTTP request / outbound webhook node fires an HTTP call to the URL of your choice the moment the scenario reaches it. The trigger can be a data change, a date, or the completion of a step.

Your server's answer is available to the rest of the scenario: {{http.status}} carries the status code, {{http.body.key}} the fields of the returned body. A scenario can therefore decide what to do next based on what your system replies — create a task if you return an error, carry on otherwise.

Answer quickly and do the work asynchronously on your side: the scenario waits for your response before it continues.

Your system calls Metaventus

The incoming webhook trigger opens the other direction. Each trigger carries a webhook key you choose (for example erp-orders) that identifies the scenario to start. Your system posts to that entry point, and the scenario runs with the data it received: create a contact, update an opportunity, send a message.

Choosing between webhook and polling

Polling the API in a loop to spot a change burns your quota and adds a delay equal to the polling period. A scenario that calls you at the moment of the event removes both. Keep polling for catch-up — after an outage on your side, say — filtering on a modification date.