Integrations & code
Call public APIs, run JavaScript or Python, sign webhooks, scope tokens, and move validated workflow definitions as JSON.
Demonstration workflow using a first-party Fluenta template.
Product detail
Code and integrations live inside the same branch structure as the rest of the customer journey, so a success and an error can be reviewed before publication.
Use an HTTP node to call a public API from a workflow when a business operation needs external data or an action. Configure the request and map the response into variables that later nodes can use.
An explicit success branch and error branch make the integration outcome part of the visible workflow rather than hidden application code.
Run JavaScript or Python where the operation needs a custom transformation or calculation. Keep the code step connected to named variables and a visible next branch so the result can be traced in the simulator.
Review the runtime limits and security constraints in the developer documentation before placing a code operation in a production workflow.
Signed webhooks verify that an incoming request is from the expected sender before it can affect a workflow. Scoped tokens limit an external API or integration to the access it needs for the declared operation.
Keep secrets out of customer messages and limit variable mapping to the data required by the request.
Move validated workflow definitions as JSON when your development process needs a portable representation. A definition should be validated before it is treated as ready to publish.
JSON portability supports review of the workflow structure; it does not bypass the configured runtime limits or security constraints.
Product detail
This illustrative flow keeps the operational contract visible from customer input to a human handoff.
The customer supplies an order ID in a message node, and the workflow stores it in an orderId variable. The variable gives the next operation a structured request value.
A missing or malformed value follows an explicit branch that asks for the information again or directs the conversation to a person.
An HTTP node calls the order API with the orderId variable. The request uses the scoped token and records the response or error in the execution trace.
The HTTP node does not assume the remote service will respond successfully; its error branch is part of the workflow.
Map response values such as fulfilment state into named workflow variables. The following condition reads those values instead of parsing an unstructured reply.
The simulator can show the mapped values and the call stack when a response does not produce the expected branch.
A condition routes a fulfilled order toward a status update and a different fulfilment state toward the appropriate customer message. If the order API fails or the state cannot be handled, the error path hands the conversation to a person with the reason.
The operator receives the transcript and captured orderId, not a bare failure notice.
Use visible HTTP, code, and webhook operations with an explicit success path, error path, and handoff reason.
Start building free