Skip to Content

Google Pub Sub Publish Message Activity

Introduction

A Google Pub Sub Publish Message activity, using its Google Pub Sub connection, publishes messages to a topic in Google Pub/Sub and is intended to be used as a target to consume data in an operation.

Create a Google Pub Sub Publish Message Activity

An instance of a Google Pub Sub Publish Message activity is created from a Google Pub Sub connection using its Publish Message activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an Activity Instance in Component Reuse.

An existing Google Pub Sub Publish Message activity can be edited from these locations:

Configure a Google Pub Sub Publish Message Activity

Follow these steps to configure a Google Pub Sub Publish Message activity:

Step 1: Enter a Name and Specify a Topic

In this step, provide a name for the activity and specify a subscription. Each user interface element of this step is described below.

The interface used in this step of the configuration of a Google Pub Sub Publish Message activity depends on the Choose Subscription option selected:

  • Inform Topic Manually: For this option, you will manually enter the topic where the messages are to be published.

  • Select Existent Topic: This option will populate a list of existing topics to choose from. To use this option, you must have the pubsub.topics.list assigned to the service account specified in the Google Pub Sub connection.

Inform Topic Manually

If Inform Topic Manually is selected for Choose Topic, this interface is presented:

Google Pub Sub Publish Message Activity Configuration Step 1 Manual

  • Name: Enter a name to identify the activity. The name must be unique for each Google Pub Sub Publish Message activity and must not contain forward slashes / or colons :.

  • Choose Subscription: Select the method for providing the topic to be used in the request:

    • Inform Topic Manually: Select to manually enter the topic where the messages are to be published.

    • Select Existent Topic: Select to choose an existing topic from a populated list. To use this option, you must have the pubsub.topics.list permission assigned to the service account specified in the Google Pub Sub connection.

  • Topic: Enter the name of the topic where the messages are to be published.

  • Continue on Error: Select to continue the activity execution if an error is encountered for a dataset in a batch request. If any errors are encountered, they are written to the operation log.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Select Existent Topic

If Select Existent Topic is selected for Choose Topic, this interface is presented:

Google Pub Sub Publish Message Activity Configuration Step 1 List

  • Name: Enter a name to identify the activity. The name must be unique for each Google Pub Sub Publish Message activity and must not contain forward slashes / or colons :.

  • Choose Subscription: Select the method for providing the topic to be used in the request:

    • Inform Topic Manually: Select to manually enter the topic where the messages are to be published.

    • Select Existent Topic: Select to choose an existing topic from a populated list. To use this option, you must have the pubsub.topics.list permission assigned to the service account specified in the Google Pub Sub connection.

  • Select a Topic: This section displays topics available in the Google Pub Sub endpoint.

    • Selected Topic: After a topic is selected, it is listed here.
  • Search: Enter any column's value into the search box to filter the list of topics. The search is not case-sensitive. If topics are already displayed within the table, the table results are filtered in real time with each keystroke. To reload topics from the endpoint when searching, enter search criteria and then refresh, as described below.

  • Refresh: Click the refresh icon Refresh icon or the word Refresh to reload topics from the Google Pub Sub endpoint. This may be useful if topics have been added to Google Pub/Sub. This action refreshes all metadata used to build the table of topics displayed in the configuration.

  • Selecting a Topic: Within the table, click anywhere on a row to select a topic. Only one topic can be selected. The information available for each topic is fetched from the Google Pub Sub endpoint:

    • Name: The name of the topic.

    • Description: The description of the topic.

    Tip

    If the table does not populate with available topics, the Google Pub Sub connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

  • Continue on Error: Select to continue the activity execution if an error is encountered for a dataset in a batch request. If any errors are encountered, they are written to the operation log.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the Data Schemas

Any request or response schemas generated from the endpoint are displayed. Each user interface element of this step is described below.

Google Pub Sub Publish Message Activity Configuration Step 2

  • Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    The Google Pub Sub connector uses the Google Pub/Sub API. Refer to the API documentation for information on the schema nodes and fields.

    Note

    The response schema for the Publish Message activity will vary depending on the configuration of the Topic selected in Step 1: Enter a Name and Select a Topic. If the selected topic has a configured schema, the request schema will have a body node with the same structure as the configured schema in Google Pub/Sub. If the selected topic does not have a configured schema, the request schema will have a body field that accepts string data (shown above).

  • Refresh: Click the refresh icon Refresh icon or the word Refresh to regenerate schemas from the Google Pub Sub endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next Steps

After configuring a Google Pub Sub Publish Message activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity Actions Menu in Connector Basics.

Google Pub Sub Publish Message activities can be used as a target with these operation patterns:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.