About the HTTP Webhook connector

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.

How it works

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:

1. The vendor sends the event payload to the configured URL.
2. Integration Service receives the payload and evaluates it against your configured event data filters.
3. If a match is found, Integration Service triggers the workflow execution through Orchestrator.

Webhook payloads are processed the same way as any other trigger events.

For more information, refer to Using the Webhook connector.

If the vendor requires a handshake, configure the challenge verification. For more information, refer to Webhook challenge verification.

Rate limits

Webhook-triggered events are subject to the following limits:

• 500 events per minute per tenant
• 100 events per minute per connection

Limitations

• Design time trigger debugging is not currently available.
• Only JSON format requests are supported.

Frequently asked questions

I pasted the Webhook URL into the provider’s UI, why is verification still not passing?

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.

I configured the challenge incorrectly, why is my connection still being created successfully?

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.

How do I use the response coming from a webhook created in Orchestrator?

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.

The webhook response is a JSON string. How do I use parts of it in my workflow?

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