Pub/Sub Source Node
Quick Reference
Google Pub/Sub Integration The integration that supplies the GCP project ID and service-account credential used to pull messages.
Subscription
The Pub/Sub subscription to consume from. Use the subscription's short ID, not its full resource path.
ex: my-subscription
Encoding The format of the message payload.
Max Messages
Maximum number of messages returned per pull request. Range: 1–1000. Default: 100.
Return immediately When checked, the pull returns right away even if no messages are available, instead of waiting.
Ack Deadline Extension (seconds)
Extra seconds to extend the message acknowledgement deadline while the workflow processes the batch. Max: 600. Default: 0.
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. Project ID and credentials come from the Pub/Sub integration you select.
Configuration
| Field | Description | Required | Default |
|---|---|---|---|
| Google Pub/Sub Integration | Selects the GCP project ID and credential used for this subscription. | No | — |
| Subscription | Pub/Sub subscription short ID (e.g. my-subscription). The project comes from the integration. | Yes | — |
| Encoding | Format used to decode the message payload. Options: CSV, JSON Object, JSON Array, JSON Lines, String Line, Text, XML. More info here. | Yes | — |
| Max Messages | How many messages to request per pull (1–1000). | No | 100 |
| Return immediately | If enabled, the pull returns instantly when the subscription is empty instead of waiting for new messages. | No | false |
| 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. | No | 0 |
Related Nodes
- Pub/Sub Sink: Publish processed records to a Pub/Sub topic
- Kafka Source: Consume streaming data from Kafka