SerialOptimistQ: Please Help
Hi Release0 Support,
I'd like to use the Webhook block to make Release0 and endpoint for an external REST API.
I've used the Set Variable block to set Result ID as resultId and logged it using the Agent Dialog Text block which confirms that I have the resultId.
I then used the HTTP Request block to POST a payload containing the resultId { message: resultId } to my external REST API.
My external REST API uses the resultId to build the url for the Webhook block endpoint. But when the REST API sends a POST request to the Release0 production endpoint I get the response "Not Found".
I suspect it is the resultId that is incorrect as sending a POST request to the test endpoint gets the response "OK".
TL;DR I think either I'm getting the wrong result id or the result id becomes stale (gets too old) by the time I use it.
Please help.
release0
Dec 4, 2025A: Hi SerialOptimist, Your suspicion is correct, but the reason for the "Not Found" error is a subtle and very important distinction in how Release0's webhooks are designed to work.
The Core Misunderstanding: Result ID vs. Webhook URL
The "Not Found" error is happening because of a fundamental misunderstanding of what a Release0 webhook endpoint is. You are trying to use the Result ID to communicate back to an in-progress agent session, but that's not what the webhook endpoint is designed for.
Agent Session (Result ID): This is a unique identifier for a single, live conversation or run of an agent. It's like a temporary session ID. You can make outbound API calls from this session, but you cannot send an inbound API call to this specific session.
The URL https://api.release0.com/v1/results/{resultId}/... does not exist for receiving data.
Webhook Trigger URL: This is a static, permanent URL that is designed to start a new session of an agent from an external source. It's a "front door" to the agent, not a "window" into an existing conversation. You find this URL in the Release0 editor when you use a Webhook as a starting event.
In summary: The Result ID is an identifier for a session, not an address you can send data to. The webhook URL is the address, and it always creates a new session.
The Correct Workflow (and How to Achieve Your Goal)
Your goal is to have an external service send data back that is related to the original session. Here is the correct, two-part pattern to achieve this:
Part A (Your Current Agent):
The agent starts, gets its Result ID, and saves its state or initial data to an external database (like Google Sheets, Supabase, etc.) using the Result ID as the key.
The agent then sends the Result ID to your external REST API.
Part B (A New "Listener" Agent):
You create a separate agent (or a separate flow starting with a webhook event) that is triggered by a static Webhook URL.
Your external REST API, after doing its work, sends its response not to the resultId URL, but to this static Webhook URL.
Crucially, the payload your API sends must include the original Result ID it received.
The "Listener" agent is triggered, receives the payload, extracts the original Result ID, and can then use that ID to look up the original session's data in your database and continue the process.
If you need additional help please add our support user support@release0.com to your workspace and contact us so we can try to better understand your use case.
Verified purchaser
Thanks a lot for getting back to me, Release0, Team! I emailed as well, and I truly appreciate your responsiveness here on Appsumo, plus the suggested fix. Cheers!