Activities

In addition to the activities available for general use, TIBCO Cloud Integration- Flogo (PAYG) supports activities that were originally created in Project Flogo™. Such activities are marked with an OSS tag on them. This allows for a seamless import of apps that were created in Project Flogo™. The Project Flogo™ activities are placed under the Default category.

If you are creating an app in TIBCO Cloud Integration- Flogo (PAYG), it is preferable to use the general purpose activities (the activities 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.

The available activities are placed under the following categories:
  • Default
  • General

You can create a flow branch from any activity except the Return activity.

To create a branch from an activity. Refer to the TIBCO Flogo® Enterprise User's Guide for steps to create a branch.

Refer to the TIBCO Flogo® Enterprise User's Guide for steps to delete an activity.

This section contains the following topics:

  • LogMessage
    LogMessage is an activity that writes a message to the log. For each application, there is a log file. You can view the logs in the Log tab.
  • SendMail
    SendMail is an activity that sends an email by way of an SMTP server.
  • InvokeRESTService
    This activity is both an outbound and inbound REST request which means that it is used to make a request to the REST service and also accept the reply returned by the service.
  • ReplyToHTTPMessage (Supported for backward compatibility only)
    This activity is not supported in TIBCO Cloud Integration- Flogo (PAYG) 2.5.0 and above. This activity is applicable only to flows that were created in previous versions of TIBCO Cloud Integration- Flogo (PAYG) (prior to version 2.5.0) that are imported into the current version.
  • Mapper
    Use this activity to define a schema to get the desired data. This activity is particularly useful to define a schema for an object of type any. In the flow, you place the Mapper activity preceding an activity whose input requires an object of data type any. This allows you to map the object of type any to the output from the Mapper activity. An advantage of using this activity is that you can construct the data for the any data type within the flow instead of fetching it from outside.
  • InvokeLambdaFunction
    Use this activity to to invoke a specific Lambda function.
Related concepts