Actions4
- Messages Actions
- Topic Subscriptions Actions
Overview
This node interacts with Google Cloud Pub/Sub to acknowledge messages received from a subscription. It is useful in scenarios where you want to confirm receipt of messages to prevent their redelivery, such as in message processing workflows or event-driven automation. For example, after pulling messages from a subscription, you can use this node to acknowledge those messages, ensuring they are not delivered again.
Use Case Examples
- Acknowledging messages pulled from a Google Pub/Sub subscription to confirm processing.
- Automating message acknowledgment in a workflow that processes events from a Pub/Sub topic.
Properties
| Name | Meaning |
|---|---|
| Project ID | Google Cloud project id where the Pub/Sub subscription exists. |
| Subscription | Name of the Google Pub/Sub subscription from which messages are acknowledged. |
| Acknowledge IDs | List of acknowledge IDs to confirm receipt of messages. Can be provided as a JSON array or as individual IDs via UI. |
| JSON Acknowledge IDs | Boolean flag to specify whether the acknowledge IDs are provided as JSON or via the UI. |
Output
JSON
success- Indicates if the acknowledgment operation was successful.
Dependencies
- Google Cloud Pub/Sub API
- Google Auth Library for authentication
Troubleshooting
- Ensure valid Google API credentials are provided; missing credentials will cause errors.
- Subscription name must be correct and accessible within the specified project.
- Acknowledging a message whose ack deadline has expired may succeed but the message might be redelivered later.
- Providing acknowledge IDs in incorrect format (JSON vs UI) can cause failures; ensure the 'JSON Acknowledge IDs' flag matches the input format.
Links
- Google Cloud Pub/Sub Acknowledge API - Official documentation for acknowledging messages in Google Cloud Pub/Sub.
