Configure the HTTP Webhook connector in Integration Service to receive real-time, event-driven callbacks from external applications without polling.

Webhooks enable applications to notify external systems in real time, reducing the need for frequent polling and minimizing API calls. Instead of periodically checking for updates, the system receives event-based callbacks only when relevant changes occur.

The UiPath HTTP Webhook connector allows you to trigger workflows directly from vendor applications. You can create instant triggers for events for any third-party application that supports outbound webhook notifications, even if it is not part of the connector catalog.

You can also apply event data filters to specify the exact conditions under which a webhook event should trigger a workflow.

The HTTP Webhook trigger generates a dynamic public callback URL. Copy and configure this URL in the vendor application's webhook settings only after your trigger has been created in Orchestrator.

When an event occurs in the vendor system:

Webhook payloads are processed the same way as any other trigger events. The connector also supports optional header-based authentication, which lets the vendor authenticate itself to UiPath on every webhook delivery using a configured header value.

For more information, refer to Using the Webhook connector.

For information on how to create a connection and configure challenge verification, if required by the vendor, refer to HTTP Webhook authentication.

The HTTP Webhook connector offers two complementary security mechanisms, both configured at connection-creation time:

For setup details, see HTTP Webhook authentication.

Webhook-triggered events are subject to the following limits:

Verification will only succeed after the trigger is created in Orchestrator and provided you have configured the challenge correctly. Note that UiPath does not perform any challenge verification on our side—the validation happens entirely on the provider’s end in order to establish trust with the destination.

UiPath does not currently validate the provider’s challenge/verification step. This validation is handled entirely by the vendor. As a result, the connection in UiPath may appear active even if the provider’s challenge verification has actually failed on their side.

Use the Get Trigger Event Output activity in your workflow and pass UiPathEventObjectId (data type=Text) as the input argument. This activity will return both the body and the headers received from the webhook.

Use the Deserialize JSON activity to convert the string into a JObject, after which you can easily access individual fields.

Yes. Enable Header-based authentication when creating or editing the connection, then configure the matching header in the vendor's webhook settings. For setup instructions, see HTTP Webhook authentication.

No. Header-based authentication uses a static, pre-shared header value. Signature-based vendors compute a fresh HMAC on every request using the payload and a shared secret — UiPath does not currently validate vendor-specific signatures. For those vendors, the available security mechanisms are URL secrecy and the vendor's challenge verification handshake.