Pub/Sub Source Node
The Pub/Sub Source node is not generally available in Fleak Data Workflow. The workflow builder offers it only to accounts where it has been enabled. For the connectors that are generally available, see Data Assets.
This page is retained for accounts where it is enabled.
Quick Reference
- Data Asset: Select a Pub/Sub subscription asset; subscription/project/authentication belong to the asset/profile.
- Encoding: Format used to decode the message payload. Options: CSV, JSON Object, JSON Array, JSON Lines, String Line, Text, XML. More info here.
- Max Messages: How many messages to request per pull (1–1000). Default:
100. - Return immediately (don't wait for messages to arrive): Node panel.
- Ack Deadline Extension (seconds): Additional seconds added to the original ack deadline while the batch is being processed (max
600). Use this when downstream processing can run long. When blank, the runtime uses0.
Configuration
Configuration keys below are relative to the node configuration. Use the field name in the panel when following instructions in the builder; required markers such as an asterisk are not part of the name.
| Field in the panel | Configuration key | Where to edit / when shown |
|---|---|---|
| Data Asset | dataAssetId | Select a Pub/Sub subscription asset; subscription/project/authentication belong to the asset/profile |
| Encoding | encodingType | Node panel — Format used to decode the message payload. Options: CSV, JSON Object, JSON Array, JSON Lines, String Line, Text, XML. More info here. Required: Yes. |
| Max Messages | maxMessages | Node panel — How many messages to request per pull (1–1000). Default: 100. Required: No. |
| Return immediately (don't wait for messages to arrive) | returnImmediately | Node panel |
| Ack Deadline Extension (seconds) | ackDeadlineExtensionSeconds | Node panel — Additional seconds added to the original ack deadline while the batch is being processed (max 600). Use this when downstream processing can run long. When blank, the runtime uses 0. Required: No. |
Overview
The Pub/Sub Source node consumes messages from a Google Cloud Pub/Sub subscription and feeds them into your workflow. Messages are acknowledged after the workflow processes them, so failures cause Pub/Sub to redeliver. Select Data Asset for the subscription; project identity and credentials come from its connection profile.
Setting behavior
Related Nodes
- Pub/Sub Sink: Publish processed records to a Pub/Sub topic
- Kafka Source: Consume streaming data from Kafka