Skip to main content
In Cognigy.AI 2025.25.0, transformers will start using the axios library for handling HTTP requests internally instead of request-promise. This change occurs to improve security and maintainability. The following HTTP request options will still be supported:
  • URL configurationuri, url
  • Request methodmethod
  • Request headers and configurationheaders
  • Request bodyform, json
  • Query parametersqs, qsStringifyOptions
  • Authenticationauth
  • Connection and networkproxy, maxRedirects, gzip, encoding
If you use other HTTP request options, review your transformer code to ensure it is compatible with the axios library before the release of Cognigy.AI 2025.25.0.
The Execution Finished Transformer converts the Flow output after a Flow execution has finished. The return value of the execution finished transformer is sent to the Endpoint. This transformer applies only to REST-based Endpoints using the output transformer. You can configure the execution finished transformer in the handleExecutionFinished function in the Endpoint settings or via CLI.

Transformer Function Arguments

The following table shows an overview of the function arguments:

Endpoint Configuration Object

Return Values

The return value of the execution finished transformer depends on the Endpoint type you are using. There is no validation of the execution finished transformer return value. If the execution finished transformer returns a falsy value, the output isn’t sent to the Endpoint. The execution finished transformer takes the outputs array from the output transformer and sends it to the Endpoint. For example, if you’re using the execution finished transformer in an Alexa Endpoint, the return value format must meet the Alexa message format. Here is an example of the correct return format for an Alexa Endpoint:
Last modified on April 21, 2026