Dedicated webhook URL

Setting up the trigger generates a single, private URL that exists only for this workflow. Any external system, script, or third party service that can send an HTTP request can post to that address, whether it is a form submission, a payment notification, or a custom application event. A Beam agent watches this URL and wakes up the moment a request lands, without needing the sender to support a specific platform. If a request is missing expected fields for the next step, the agent routes it to a person to confirm before applying whatever rule comes next.

Raw request capture

Every incoming call is captured with its headers, query parameters, and body exactly as sent, rather than a simplified summary. A Beam agent reads this raw payload to pull out the specific fields a downstream rule needs, for example an order ID, a status code, or a customer email address. Because the format of incoming requests can vary by sender, the agent applies the approved parsing rule and, where a payload does not match the expected shape, routes it to a person to check rather than guessing at missing or malformed data.

Immediate trigger on arrival

The workflow starts the moment a request hits the URL, with no polling delay built into the wait. This matters for time sensitive events, such as an alert from a monitoring tool or a form submitted by a customer, where a Beam agent needs to act within seconds rather than minutes. The agent applies the next approved step immediately, whether that is creating a record or notifying a channel. Requests that arrive outside expected volume or pattern, suggesting a misconfigured sender, are routed to a person to investigate.