New: Enveu Flow is now generally available — automate media operations alongside Experience Cloud. Learn more
Flow Custom

HTTP + Enveu

Custom HTTP integration. Call any external API or receive webhooks from any system not covered by built-in plugins.

Best forConnecting any external API, internal service, or custom endpoint not covered by built-in plugins — as a trigger or action in any workflow.
Make HTTP GET, POST, PUT, and DELETE requests to any API endpoint. Receive and process incoming webhooks as workflow triggers. The most flexible plugin in Flow - use to connect any service that has an API.

Inputs & outputs

Inputs
URLAPI endpoint to call or webhook URL to listen on
MethodHTTP method — GET, POST, PUT, PATCH, DELETE
HeadersRequest headers including authorization tokens
BodyRequest payload — JSON, form data, or raw
Outputs
Response bodyParsed JSON or raw response from the API
Status codeHTTP response status confirming success or failure

Triggers & actions

Triggers
Incoming webhookAn external system POSTs to a Flow-generated webhook URL to start a workflow
Polling triggerFlow polls an external API endpoint on a schedule and fires when conditions are met
Actions
GET requestMake an authenticated HTTP GET request to any external API
POST requestSend a JSON payload to any external API endpoint
PUT requestUpdate a remote resource via HTTP PUT with configurable body
PATCH requestPartially update a remote resource via HTTP PATCH
DELETE requestRemove a remote resource via HTTP DELETE
Parse responseExtract fields from a JSON API response for use in downstream steps

Example workflow

Webhook receivedHTTP trigger
Parse payloadHTTP action
Process dataFlow engine
Call downstream APIHTTP action
NotifySlack

Frequently asked questions

What is HTTP + Enveu?
Custom HTTP integration. Call any external API or receive webhooks from any system not covered by built-in plugins.
What authentication methods does the HTTP plugin support?
Flow's HTTP plugin supports Bearer token, API key (header or query param), Basic auth, and unauthenticated requests. Credentials are stored securely in the Flow vault and injected at runtime.
Can Flow receive incoming webhooks from any external service?
Yes. The HTTP incoming webhook trigger gives you a unique URL that any external service can POST to. Flow parses the payload and makes the data available to downstream workflow steps.
Can Flow parse and extract values from HTTP response bodies?
Yes. The parse response action supports JSONPath expressions to extract specific values from API responses. Extracted values can be mapped to variables used in subsequent workflow steps.
Does Flow retry failed HTTP requests automatically?
Yes. You can configure automatic retry logic for HTTP actions - specifying the number of retries, backoff interval, and which HTTP status codes should trigger a retry.

Launch with Enveu + HTTP

See how Enveu works with HTTP to power and automate OTT at scale.