How can we help?

Webhooks are a mechanism that allows one application to send information to another application when a particular event occurs. They are commonly used to connect software systems and support event-driven business processes. Unlike a traditional API request, where one system actively requests information, a webhook is generally sent by the system where the event occurred. How does a webhook work? A typical webhook process involves the following steps: 1. An event occurs in an external application. 2. The application identifies that the event matches a configured webhook subscription. 3. The application sends an HTTP request to a designated endpoint. 4. The receiving system validates and processes the request. 5. The receiving system returns an appropriate HTTP response. For example, a business application may send a webhook when an order is created or when a payment status changes. These are general webhook examples, not confirmation that a particular event is supported by Polyosync. What is the difference between APIs and webhooks? API request A system initiates a request to retrieve information or perform an operation. Webhook A system sends an event notification to another system, usually without waiting for the receiving system to request the information. Both approaches can be used together. What are webhooks useful for? Common applications include: 1. Event-driven notifications. 2. Order and transaction updates. 3. Customer activity events. 4. Status changes in external applications. 5. Coordination between business systems. 6. Triggering downstream processing when supported. Can webhooks trigger Polyosync workflows? This depends on the webhook receiving and trigger functionality implemented for the relevant workflow. The existence of a webhook feature in an external service does not automatically mean that Polyosync can receive or process every event. Can Polyosync send webhooks to other applications? Outbound webhook functionality must be supported and configured for the intended operation. Incoming and outgoing webhooks are separate capabilities. Are webhooks always delivered instantly? Not necessarily. Delivery timing depends on the sending service, network conditions, retry policies, and processing behavior. Are webhooks guaranteed to arrive only once? No. Depending on the provider, events may be retried or delivered more than once. Systems processing webhooks should account for possible duplicate events. Do webhooks contain sensitive information? They can. Webhook payloads may include personal, commercial, or operational data. Only the information required for the intended operation should be processed. Recommended approach Before using webhooks, determine the event source, expected payload, authentication method, receiving endpoint, and required processing behavior. Validate the complete event flow before relying on it for business-critical operations.