HTTP_TRIGGER

What it does

Trigger: fires on an inbound HTTP/webhook call.

Inputs & outputs

Configuration

No configuration.

Example

How it works

When an HTTP_TRIGGER node is the start of a Workflow, EzFlow registers an HTTP endpoint at:

/api/v1/trigger/{workflowId}/{branchName}/{endpointName}

Any HTTP method (GET, POST, PUT, PATCH, DELETE) is accepted; EzFlow matches the incoming request against the node's Request Method and Endpoint Name fields. If the node has authentication enabled, callers must supply Authorization: Bearer <token> or the request is rejected with 401. On success, the full request body is placed on the body output port and flows into downstream nodes.

Example

Scenario: A CRM posts a new-contact event to EzFlow, which sends the contact a welcome email.

1. Add an HTTP_TRIGGER node. Set Request method to POST and Endpoint name to contact-created.
2. Your CRM calls:

   POST https://api.ezflows.app/api/v1/trigger/<workflowId>/main/contact-created

   with a JSON body:

   { "email": "alice@example.com", "name": "Alice" }

3. Wire body.email → sendTo and body.name into a MAPPER node to compose a greeting, then connect to a SEND_MAIL node.

Each call creates a tracked job you can monitor from the Jobs view.