Published at: 2026-10-12
Trigger and Action Configuration
Configure the connector’s trigger events and execution actions.
Overview
A trigger fires a data flow when an event occurs. The application system that produces the trigger event is the trigger system. Action execution is similar to Trigger operation. The difference is that a Trigger can serve as the first node of an integration flow, whereas an API configured as an Action cannot serve as the first trigger event of an integration flow.
Before You Begin
❗
-
Role permission: Your organization must be included in the limited rollout enabled by R&D to access the Connector Development page
-
Prerequisite configuration: You understand the target system’s trigger event types and API requirements
Step 1: Choose the Trigger Event
Based on real system requirements, choose which events serve as Triggers and select New.
Real-time trigger: when a trigger event occurs, the application system automatically pushes data to the integration platform, and the platform responds and executes immediately.
Step 2: Configure Trigger Fields
Configure the corresponding fields according to the API requirements.
Step 3: Configure the Rest Hook
If the event needs real-time triggering, select Rest Hook. Hook addresses have two levels:
- Generated per integration flow: each integration flow has a different Hook address, used to distinguish different events
- Generated per account: system level (the account corresponding to the system authorization), with multiple events sharing one Hook address
The Hook address is generated after the connector configuration is complete, by entering an integration flow and selecting the corresponding event.
Step 4: Configure the Subscription Request
Some SaaS systems support dynamically registering the Hook address to the other system through the API. In this case, configure the corresponding API and parameters according to the other system’s API documentation. In the subscription request, pass the platform-generated callback address to the external system, referencing it with
path("['input_data']['bundleUrl']").Step 5: Configure Polling
If the event needs polling, configure the polling interval or a cron expression. Each time the platform’s polling framework runs, it automatically computes a set of query parameters and packs them into the
pollingTimeArg parameter bundle.Polling Placeholders
| Placeholder | Meaning | Value description |
|---|---|---|
path("['input_data']['pollingTimeArg']['startTime']") |
The start of this query’s time window | Millisecond timestamp (13 digits). Takes the “time when data was last pulled”; if no data was pulled before, goes back roughly 28 hours |
path("['input_data']['pollingTimeArg']['endTime']") |
The end of this query’s time window | Millisecond timestamp, i.e., the execution time of this polling run |
path("['input_data']['pollingTimeArg']['limit']") |
Rows per page | Fixed at 100 by the platform; you do not need to set it |
path("['input_data']['pollingTimeArg']['offset']") |
Pagination offset | Starts at 0 for the first page and auto-increments by 100 each page; the framework keeps paging until done (single-run limit of 1 million rows) |
Polling Configuration Points
You do not need to fill in values yourself. Simply use placeholders in the connector’s request configuration (URL, Query parameters, Header, request body) to “pull out” the four values, then pass them to the target system’s query API.
💡
The time unit is milliseconds. If the target API expects a second-level timestamp, put the parameter into the Query parameter or request body value and divide the whole expression:
path("['input_data']['pollingTimeArg']['startTime']") / 1000.Configure the Action Type
Action execution is similar to Trigger operation, and the configuration method is the same.
Expected Result and Verification
After configuration is complete, Trigger events fire normally and Action operations execute normally.
Verification method:
- Enter an integration flow and select the corresponding event to generate the Hook address.
- Fire an event once and check whether the integration flow responds as configured.
- If it does not respond, check the trigger fields, subscription request, and polling configuration.