Triggers

In addition to the Receive HTTP Message and Timer Trigger available for general use, TIBCO Cloud Integration - Flogo (PAYG) supports triggers that were originally created in Project Flogo™. This allows for a seamless import of apps that were created in Project Flogo™. The Project Flogo™ triggers are marked with the OSS abbreviation on them.

If you are creating an app in TIBCO Cloud Integration - Flogo (PAYG), it is preferable to use the general purpose triggers (the triggers that do not have an OSS tag on them), since they are more robust in functionality.

Refer to https://github.com/project-flogo/contrib for details on the activities that are marked with an OSS tag.

Trigger configuration fields are grouped into Trigger Settings and Handler Settings. A single trigger can be associated with multiple handlers.
  • Trigger Settings - these settings are common to the trigger across all flows that use that trigger. If and when a flow attached to the trigger changes any Trigger Settings field, the change gets propagated to all flows attached to the trigger. A warning message gets displayed saying so and asking you to confirm before the changes are committed.
  • Handler Settings - these settings are applicable to a specific flow attached to the trigger. Hence, each flow can set its own values for the Handler Settings fields in the trigger. To do so, open the flow and click on the trigger to open its configuration dialog. Click the Settings tab and edit the fields in the Handler Settings section.
Note: You cannot create a flow branch from a trigger.
Note: You can create the trigger at the time of flow creation or create a blank flow to begin with and attach the flow to one or more triggers at a later time after the flow has been created. If you anticipate that you will need to attach the flow to multiple triggers, be sure to create a blank flow and attach it to the triggers as needed. If you attach a flow to a trigger during flow creation, you cannot modify the trigger settings from within the flow. Refer to the section. "Selecting a Trigger When Creating a New Flow" in the TIBCO Cloud™ Integration - Flogo® (PAYG) User's Guide for more details.

For triggers that have an output, the output from the trigger becomes the input to the flow. Likewise, the output from the flow becomes the reply from the trigger.

This section contains the following topics:

  • Timer Trigger
    Use the Timer Trigger trigger as a process starter when creating flows designed to be activated without external input. It is useful when you want your flows to run at certain time intervals. You can configure the Timer Trigger trigger to activate the flow multiple times at a specified interval.
  • REST Trigger - ReceiveHTTPMessage
    Use the ReceiveHTTPMessage REST trigger when creating flows that require invoking RESTful web services that provide some input necessary to activate the flow. The ReceiveHTTPMessage trigger exposes your flow as an API, making it accessible by other apps running on either TIBCO Cloud™ or elsewhere. This trigger must be configured to set up the fields for a request that the server receives from a REST client.
  • GraphQL Trigger
    The GraphQL Trigger lets the Flogo app act as the GraphQL server. To use this trigger, you simply upload your GraphQL schema and TIBCO Cloud Integration - Flogo (PAYG) automatically creates the flows corresponding to each query or mutation field in your schema.
  • gRPC Trigger
    The gRPC trigger acts as the server to the gRPC clients. You create the trigger when you create a flow that gets attached to the trigger.
Related concepts