4.7k
Reference

Nodes

Full catalog of the 81 nodes available in the builder. Navigate with the Previous and Next buttons, or via the sidebar.
Use to navigate, or / to search.

Demo placeholderThe node picker, live on the canvas
Triggers & Inputs

API Endpoint Node

HTTP Trigger

Exposes an HTTP route in your workflow. Define the method (GET, POST…) and the path. The node receives the incoming request and passes it to the following nodes with headers, body, and query params.

POST /users
POST/users
Demo placeholderAPI Endpoint node in a real workflow

Connections

4 connection points
data-inInputhandle Top

Additional data injected from an upstream node

any

config-inInputhandle Left

Environment variables injected by an ENV node (API keys, secrets)

EnvConfig — { [key: string]: string }

data-outOutputhandle BottomRequired

Full payload of the incoming HTTP request — body, headers, query, and route params

{ body: any, headers: Record<string,string>, query: Record<string,string>, params: Record<string,string>, method: string }

data-out-rightOutputhandle Right

Alternative side output — same payload as data-out, for branching a second flow

{ body: any, headers: Record<string,string>, query: Record<string,string>, params: Record<string,string>, method: string }

Use Cases

  • 1

    Entry point of a REST API: expose POST /users to create a user account and chain to Validation → SQL

  • 2

    Incoming Stripe webhook: POST /webhooks/stripe — verify the signature then route to Payment

  • 3

    GET /reports/:id endpoint to generate a PDF report on demand and return it via Response

  • 4

    PATCH /settings to let a frontend update user preferences, gated by Auth

Tips

  • Chain immediately with an Auth node to secure the route before any business logic

  • testPayload and testHeaders let you simulate POST/PUT requests from the builder without deploying

  • Route parameters (e.g. :id in /users/:id) are available in data.params.id — no need to parse manually

  • For third-party webhooks, connect data-out-right to a Logger to keep a record of incoming payloads

Configuration

PropertyTypeDefaultDescription
endpointMethod"GET"|"POST"|"PUT"|"DELETE"|"PATCH""GET"Accepted HTTP method
endpointPathstring"/api/endpoint"Route path (e.g. /users/:id)
endpointAuthbooleanfalseRequires an authentication token
testPayloadstring (JSON)Payload injected during manual execution from the builder
testHeadersstring (JSON)Headers injected during manual execution
1 / 81

Was this page helpful?

Nodes | Fimaflow