From scheduled to event-driven: Synesty becomes more flexible

Many integrations do not need to regularly “check” whether something has happened. They should react exactly when something happens.

With our new Webhooks, this is now possible: External systems can call Synesty directly when an event occurs and either start a Flow or send data straight to a Datastore.

This adds event-driven integrations to the classic scheduled processing model.

A typical example: Instead of checking every 30 minutes whether new orders are available in an e-commerce system, the shop system can notify Synesty directly as soon as the relevant event occurs. The corresponding Flow starts immediately and can process the provided data.

Incoming webhook events are processed reliably through a queue. If the previous Flow is still running, the next event simply waits to be processed instead of being rejected as before.

For use cases with a very high number of individual events, webhook data can alternatively be written directly to a Datastore first and then processed in batches by a Flow – for example every 15 minutes. This makes it possible to choose between immediate processing and efficient batch processing depending on the use case.

Webhooks in Synesty explained in the video

In our how-to video, we show you step by step how webhooks work in Synesty, how to set up a webhook, and how to process incoming data either directly via a Flow Trigger or first collect it in a Datastore and process it in batches afterwards.

Das Video wird bei Klick von Youtube geladen und abgespielt. Dabei stellt Ihr Browser eine Verbindung zu den Youtube-Servern her. Es gelten die Datenschutzhinweise von Google / Youtube.

More options for different integration patterns

With Webhooks, Flows can now be integrated even more flexibly into different architectures:

• Scheduled, when processes should run at regular intervals.
• Event-driven, when an external system should trigger processing immediately.
• Batch-based, when many individual events should first be collected and then processed efficiently together.

Learn more about Webhooks in our documentation