HTTP — Custom HTTP & Webhook Integration
Make HTTP requests and receive webhooks in Enveu Flow. Connect any API or service to your media operations workflows without custom integration code.
What this integration does
Make HTTP requests and receive webhooks in Enveu Flow. Connect any API or service to your media operations workflows without custom integration code.
Best for
Connecting 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
URL
API endpoint to call or webhook URL to listen on
Method
HTTP method — GET, POST, PUT, PATCH, DELETE
Headers
Request headers including authorization tokens
Body
Request payload — JSON, form data, or raw
Outputs
Response body
Parsed JSON or raw response from the API
Status code
HTTP response status confirming success or failure
Triggers & actions.
Triggers
Incoming webhook
An external system POSTs to a Flow-generated webhook URL to start a workflow
Polling trigger
Flow polls an external API endpoint on a schedule and fires when conditions are met
Actions
GET request
Make an authenticated HTTP GET request to any external API
POST request
Send a JSON payload to any external API endpoint
PUT request
Update a remote resource via HTTP PUT with configurable body
PATCH request
Partially update a remote resource via HTTP PATCH
DELETE request
Remove a remote resource via HTTP DELETE
Parse response
Extract fields from a JSON API response for use in downstream steps
Example workflow.
Webhook received
HTTP trigger
→
Parse payload
HTTP action
→
Process data
Flow engine
→
Call downstream API
HTTP action
→
Notify
Slack
Used in these workflows.
Works well with
Frequently asked questions.
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.
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.
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.
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.