Reference5 min readUpdated 2026-06-29
GCP Pub/Sub Actions in n8n Reference
A field-tested reference of every GCP Pub/Sub action you'll use in n8n automations.
Key takeaways
- Idempotent creates.
- Merged updates.
- Indexed searches.
- Approved deletes.
Here are the GCP Pub/Sub actions we reach for in n8n every week, with the gotchas we learned the hard way.
Create
Idempotency key required. Store the GCP Pub/Sub ID for reference.
Update
Merge, never overwrite. Track prior state in Postgres for audit.
Search
Prefer indexed lookups; avoid unfiltered scans that hit rate limits.
Delete
Soft-delete when possible. Hard-delete only via a dedicated approval workflow.
Frequently asked questions
- Bulk ops?
- Use SplitInBatches + backoff.
- Concurrency?
- Per-key lock in Redis avoids double writes.
- Errors?
- Retry with exponential backoff up to 5 attempts.
- Testing?
- Sandbox GCP Pub/Sub account or a dedicated test workspace.