Trigger an Online ChatFlow
Operation description
After triggering an online flow, if your flow contains components that incur costs for cloud products, such as message sending or function calls, please ensure you fully understand the billing methods and prices of the related products before using this interface.
Debugging
Authorization information
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| FlowCode | string | Yes | Flow code. | f4912c16943b4dfba44bd6fedacf8c70 |
| Data | object | No | Input parameters in Key-Value format. The Key must match the input strategy configured at the start node of your flow. | {"my_biz_data_0": "hi", "my_biz_data_1": "1024"} |
| Uuid | string | No | Unique event ID used for idempotent triggers. Do not include any business semantics; you can retrieve this parameter within the flow after triggering. | c68622e6-5f0d-c8a4-af41-e949c2a7580e |
| OutId | string | No | External system transaction number, used to associate with external business system transactions. You can retrieve this parameter within the flow after triggering. | 8d4acf7e-e360-eb83-6d74-fcf9c4538fda |
| ClaimTimeMillis | long | No | The declared occurrence time of the event, usually the time when the request was constructed, in milliseconds timestamp. | 1731502129000 |
| DiscardTimeMillis | long | No | The time when the event should be discarded, i.e., the expiration time. If this field is specified, the message will be discarded if it exceeds this time, in milliseconds timestamp. | 1731502729000 |
None.
Response parameters
Examples
Sample success responses
JSONformat
{
"AccessDeniedDetail": "",
"RequestId": "",
"Message": "",
"Data": {},
"Code": "",
"Success": true
}Error codes
For a list of error codes, visit the Service error codes.