Skip to main content

HTTP Destination

Flowlyze's HTTP destination allows sending data to external systems via HTTP requests, one for each message in the queue or one per message block. The request is built based on configured parameters (method, endpoint, headers, query string) while the body matches the JSON payload derived from the single record.
The operation outcome is determined exclusively by the status code returned by the destination system: any value between 200 and 299 is considered a success.

Status Code

Any HTTP status code between 200 and 299 is considered a success. All other codes (3xx, 4xx, 5xx) are treated as errors and trigger the configured retry policies.

Configurable Parameters​

The HTTP destination provides the following parameters, all modifiable:

  • URL: destination endpoint of the call.
  • Method: HTTP method used (e.g. POST, PUT, PATCH, DELETE).
  • Headers: set of custom headers to include in the request.
  • Query Params: query parameters added to the URL.

All string-type fields support the use of variables, both global and local, allowing dynamic configuration based on the operational context.

Authentication​

The HTTP destination supports the same authentication protocols available for the HTTP source, allowing consistent alignment of security modes.

Planned Features (TBD)​

Evolutions are planned to extend the flexibility and transformation capabilities of the HTTP destination:

  • Using message fields as dynamic templates: Applying message values to URL, query, and header parameters, with direct substitution during request generation.
  • Body rewriting: Ability to define a custom body without going through low-code components.
  • Advanced response interpretation: Analysis of the response body content to determine the operation outcome, going beyond the model based exclusively on status code.
  • Batch message sending: Sending multiple entities in a single call, with definition of the aggregated data model and ability to interpret the response to evaluate the outcome of each message, similar to the Custom Adapter behavior but without the need for a predefined protocol.