How can we help you?
The Trigger via API setting provides a read-only reference for triggering a specific Titan Flow project from an external system.
It exposes the exact request structure required to call the Flow, including the endpoint, authentication details, and expected parameters. This information is generated automatically based on the Flow configuration and is intended to be copied and used outside of Titan.
This view does not execute, test, or configure the Flow. It exists to make external triggering predictable and consistent, without requiring users to manually construct API requests.
Not all Flows are initiated from within the Titan interface.
In many implementations, execution begins in external systems such as backend services, third-party applications, or integration layers. These systems require a reliable way to invoke a specific Flow while ensuring the request structure matches the Flow’s definition.
The Trigger via API setting supports this model by exposing the information required to invoke a Flow externally, without shifting Flow configuration or logic outside of Titan.
Titan surfaces Flow trigger details directly within the Flow settings to bridge the gap between Flow configuration and external execution.
By presenting a complete, copy-ready request, Titan ensures that external systems can trigger Flows accurately while keeping Flow logic centralized and governed inside the platform. This reduces setup errors, avoids mismatched parameters, and provides a single source of truth for how a Flow should be invoked externally.
The Trigger via API setting complements the Flow API by making invocation details visible at the Flow level, where users already define and manage workflow logic.
This opens a modal displaying all API trigger information for the selected Flow.
The Trigger via API modal is informational only.
You can:
You cannot:
Closing the modal does not affect the Flow.
The cURL section displays a complete request that can be used to trigger the Flow externally.
It includes the API endpoint, required request headers, the API key, and a request body containing the Flow input parameters. All values are generated automatically based on the Flow configuration and are read-only.
This cURL command can be copied and used directly in an API client. For example, pasting it into Postman and sending the request will trigger the Flow.
The URL section displays the endpoint used to trigger the Flow.
Key points:
This URL matches the endpoint used in the cURL command.
The API Key section shows how authentication is handled.
It includes:
The API key must be included as a request header when triggering the Flow.
The Variables section lists the input parameters the Flow expects.
Each variable:
These variables are included in the cURL request payload and must be provided when triggering the Flow.
A typical usage flow looks like this:
The Flow runs using the variables provided in the request.
