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/TIBCOSoftware/flogo-contrib for details on the activities that are marked with an OSS tag.

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 add one or more triggers to it at a later time after the flow has been created. If you anticipate that you will need multiple triggers for a flow, be sure to create a blank flow and add the triggers as needed. If you attach a trigger to a flow during flow creation, you will not be able to modify it or add triggers to the flow once such a flow has been created.
The following triggers are available for you to use:
  • Receive HTTP Message
  • Receive HTTP Message (OSS)
  • Timer Trigger
  • Timer (OSS)
  • Start Flow as a Function in Lambda (OSS)
  • 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
    Use the REST trigger, ReceiveHTTPMessage, when creating flows that require invoking RESTful web services that provide some input necessary to activate the flow. The ReceiveHTTPMessage trigger is used when you want to expose your flow as an API, making it accessible by other apps running on either the 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.
Related concepts