GCP PubSub Connector
Overview
The GCP PubSub Connector allows you to receive messages from and publish messages to the PubSub service. The available features include:
- GCPPubSubSubscribe: Subscribes to a specific SubscriptionID in a given project. While it’s recommended to call this action in an After Startup Microflow, it’s not mandatory
- GCPPubSubUnsubscribe: Unsubscribes from a specific SubscriptionID in a given project. It’s recommended to call this in a Before Shutdown Microflow, but it’s not mandatory
- GCPPubSubPublish: Publish message to a specific topic in a given project. While it’s recommended to call this action in an After Startup Microflow, it’s not mandatory
- GCPPubSubCleanPublisher: Clean and destroy all publishers in a given project. It’s recommended to call this in a Before Shutdown Microflow, but it’s not mandatory
Documentation
Typical usage scenario
The GCP PubSub Connector allows you to receive messages from and publish messages to the PubSub service
Features and limitations
GCPPubSubSubscribe:
Subscribe to a specific SubscriptionID within a project and begin listening for incoming messages, which will then be forwarded to the designated Microflow, While it’s recommended to call this action in an After Startup Microflow, it’s not mandatory.
GCPPubSubUnsubscribe:
Unsubscribes from a specific SubscriptionID in a given project. It’s recommended to call this in a Before Shutdown Microflow, but it’s not mandatory.
GCPPubSubPublish:
Publish message to a specific topic in a given project. While it’s recommended to call this action in an After Startup Microflow, it’s not mandatory.
GCPPubSubCleanPublisher:
Clean and destroy all publishers in a given project. It’s recommended to call this in a Before Shutdown Microflow, but it’s not mandatory.