Build an HTTP Endpoint

Use an HTTP-triggered workflow when another application needs to call your automation through a URL.

URL, Webhook, or Form trigger
  → validate and transform request data
  → perform work
  → Respond Text, JSON, HTML, File, Status, or Redirect

Choose the trigger

Trigger	Use it for	Request data
URL	General endpoints that accept common HTTP methods and text or binary bodies	Path, method, query, headers, body
Webhook	Services that send a JSON `POST` webhook	Path, headers, parsed JSON body
Form	Browser form submissions and optional hosted form HTML	Path, method, query, fields, files

The trigger is selected when you create the workflow. If the upstream service has a documented webhook format, use Webhook. Use URL for a custom API surface and Form for browser-submitted fields or uploads.

Validate the incoming data

Trigger Data exposes the request values. Treat all of them as untrusted.

Check required properties before using them.
Use type checks and conversion actions when a value may arrive as text.
Validate structured bodies with Validate JSON Schema.
Return a clear 4xx response when the request cannot be processed.

Do not place secrets in query parameters. URLs are commonly stored in browser, proxy, and service logs. Prefer a request header or body field when the sending service supports it.

Return one response

Add the response action that matches the endpoint contract:

Response action	Result
Respond Text	Plain text with a configurable status
Respond JSON	A JSON response body
Respond HTML	Rendered HTML
Respond File	A downloadable or inline file
Respond Status	Status code without a body
Redirect	Redirect to another URL

Only response actions compatible with the selected trigger can be added. If several branches can respond, design them so one branch wins for each request.

Example: create a JSON endpoint

Create a workflow with the Webhook trigger.
Read the parsed body from Trigger Data.
Validate the required fields.
Run the actions that process the request.
Build a result object.
Connect it to Respond JSON.
Wait for Saved!, enable the workflow, and send a representative POST.
Inspect the run and the caller’s response.

For an error branch, connect the validation result to a condition and return:

{
  "ok": false,
  "error": "email is required"
}

with status 400. The success branch can return status 200 or 201.

Operate the endpoint

Keep the workflow Live while callers depend on it.
Watch Run History for failed requests and node errors.
Preserve a stable response shape when downstream applications parse it.
If you pause the workflow, new requests produce paused-workflow failures; they are not queued for later.

See HTTP and webhook triggers for payload limits, response timing, and the differences between the three trigger types.

Get Started

Understand the Basics

Build Workflows

Triggers & Events

Test & Operate

Projects & Connections

Recipes

Choose the trigger

Validate the incoming data

Return one response

Example: create a JSON endpoint

Operate the endpoint

​Choose the trigger

​Validate the incoming data

​Return one response

​Example: create a JSON endpoint

​Operate the endpoint

Choose the trigger

Validate the incoming data

Return one response

Example: create a JSON endpoint

Operate the endpoint