Skip to content

Connectors / Developer tools · Connector

Start workflows from any webhook

Give any service a URL to call, and start a workflow the moment it does.

What can you do with the Webhook Trigger connector?

Most apps can call a URL when something happens. The Webhook Trigger gives a workflow its own URL and starts the workflow when a request arrives. You choose how it replies: an immediate HTTP 200, or your own status, body and headers once the workflow has finished.

Connects through
Connector

Automate & integrate Webhook Trigger

Automating Webhook Trigger business processes or integrating Webhook Trigger data is made easy with Tray.ai.

Use case

React to events as they happen

Start a workflow when a form is submitted, a payment succeeds or a ticket changes, instead of checking the app on a schedule.

  • No polling delay
  • Works with any sender
  • One URL per workflow

Use case

Build simple APIs

With Await workflow and respond and a Trigger Event Reply step, a workflow can answer its caller, such as returning a lookup result, or a 404 when nothing matches.

  • Custom status and body
  • Your own headers
  • Answers within five minutes

Use case

Accept calls from a browser

Turn on browser requests so a web form or app can call a workflow directly, and add the access-control headers in your reply.

  • Forms call workflows directly
  • You control the headers
  • Off until you turn it on

Ready to solve your Webhook Trigger integration challenges?

See how Tray.ai makes it easy to connect, automate, and scale your workflows.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

Challenges Tray.ai solves

Common obstacles when integrating Webhook Trigger — and how Tray.ai handles them.

Challenge

Securing a public URL

Anyone who finds a webhook URL can send it requests.

How Tray.ai helps

Require a token in the X-CSRF-TOKEN header, kept in a Tray authentication, and requests without it are rejected. Add the sender's own checks, such as signatures or account IDs, where it offers them.

Challenge

Long-running work

A caller waiting on a reply will time out if the work takes too long.

How Tray.ai helps

Await workflow and respond waits up to five minutes. For longer jobs, reply with a 200 straight away and send the result back later with the HTTP Client.

Challenge

Large payloads

Some senders post big bodies or file uploads.

How Tray.ai helps

A standard webhook payload can be up to 1 MB, with larger bodies made available at a URL, and multipart requests can be up to 10 MB.

See Webhook Trigger working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.