Creating a Flow Trigger
Flow trigger types include APIG, SMN, and timer.
Creating a Timer Trigger
- Log in to the FunctionGraph console, and choose Flows in the navigation pane.
- On the Flows page, find the target flow, and click Edit.
- Click the Start node. On the displayed page, click Create Trigger and set Trigger Type to Timer.
Figure 1 Timer trigger
- Set the trigger information. As shown in Table 1, parameters with an asterisk (*) are mandatory.
Table 1 Timer trigger information Parameter
Description
* Rule
Triggering rule of the timer. Currently, only cron expressions are supported.
* Cron Expression
Specifies the date and time when the flow will be scheduled. For details, see Cron Expressions for a Function Timer Trigger.
Additional Info
Must be in JSON format and contain an input. The value of input will be passed to the flow.
- Click Create.
Creating an APIG (Shared) Trigger
The shared gateway is no longer available. Only existing customers who previously used this feature can continue using it.
APIG flow triggers support only IAM authentication.
- Return to the FunctionGraph console, and choose Flows in the navigation pane.
- On the Flows page, find the target flow, and click Edit.
- Click the Start node. On the displayed page, click Create Trigger and set Trigger Type to API Gateway (shared).
Figure 2 API Gateway (shared) trigger
- Set the trigger information. As shown in Table 2, parameters with an asterisk (*) are mandatory.
Table 2 APIG (shared) trigger information Parameter
Description
* API Group
An API group facilitates management of APIs used for the same service.
In this example, select APIGroup_test.
* Environment
An API can be called in different environments, such as production, test, and development. APIG supports environment management, allowing you to define different request paths for an API in different environments.
To ensure that the API can be called, select RELEASE.
* Visibility
Options: Public and Private.
* Path
Path for requesting the API.
Format: /users/projects
* Method
The API calling method. Options: GET, POST, DELETE, PUT, PATCH, HEAD, OPTIONS, and ANY.
ANY indicates that the API can be called using any request method.
- Click Create.
Creating an APIG (Dedicated) Trigger
- APIG flow triggers support only IAM authentication.
- Ensure that you have created a dedicated gateway before this operation. For details, see Buying a Dedicated Gateway.
- Return to the FunctionGraph console, and choose Flows in the navigation pane.
- On the Flows page, find the target flow, and click Edit.
- Click the Start node. On the displayed page, click Create Trigger and set Trigger Type to API Gateway (dedicated).
Figure 3 API Gateway (dedicated) trigger
- Set the trigger information. As shown in Table 3, parameters with an asterisk (*) are mandatory.
Table 3 APIG (dedicated) trigger information Parameter
Description
* Gateway
Select a dedicated gateway.
* API Group
An API group facilitates management of APIs used for the same service.
In this example, select APIGroup_test.
* Environment
An API can be called in different environments, such as production, test, and development. APIG supports environment management, allowing you to define different request paths for an API in different environments.
To ensure that the API can be called, select RELEASE.
* Visibility
Options: Public and Private.
* Path
The path for requesting the API.
Format: /users/projects
* Method
The API calling method. Options: GET, POST, DELETE, PUT, PATCH, HEAD, OPTIONS, and ANY.
ANY indicates that the API can be called using any request method.
- Click Create.
Creating an EG Trigger
- Return to the FunctionGraph console, and choose Flows in the navigation pane.
- On the Flows page, find the target flow, and click Edit.
- Click the Start node. On the displayed page, click Create Trigger and set Trigger Type to EventGrid.
- Select an event channel and source. Events from this source will trigger the flow.
Figure 4 EG trigger
- Set the trigger information, as shown in Table 4. Parameters with an asterisk (*) are mandatory.
Table 4 Timer trigger information Parameter
Description
* Provider
EG event source provider. Huawei Cloud and custom event sources are supported.
* Event channel
Receives events from the specified source to trigger the function flow.
* Event source name
Event sources include Huawei Cloud services and custom applications. They produce events and publish them to EG.
Event types
Types of events that will trigger the function flow.
- Click Create.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot