Streaming & Messaging · Integration
Google Cloud Pub/Sub
Add Google Cloud Pub/Sub to your product for your customers, and give your AI agents governed access to it.
Embed a Google Cloud Pub/Sub integration so your customers can publish to and consume from their own topics and subscriptions from inside your product, which is how most of them already move events between systems. Access is scoped per tenant with least-privilege credentials, delivery is acknowledged so work is not lost, and every call is logged. fastn handles credential storage, retries, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers publish messages to their own topics from events in your product.
Consume messages from a subscription so your product reacts to their existing pipelines.
Read subscription backlog so a growing queue is visible where users work rather than in a console.
Trigger your product when a message lands on a dead-letter topic.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent publishes a message to hand work to another system within governed permissions.
An agent reads backlog size before deciding whether to act.
An agent reacts to a dead-letter message and gathers the failure detail an engineer needs.
Example prompt
Show subscriptions with a growing backlog and how many messages have landed on each dead-letter topic today.
Set up Google Cloud Pub/Sub in 4 steps
- 01Open the Google Cloud Pub/Sub connector from your fastn dashboard.
- 02Have each customer authenticate their own Google Cloud project with least-privilege scopes.
- 03Map the topics and subscriptions your product uses, then enable the actions and triggers you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Google Cloud Pub/Sub integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Google Cloud Pub/Sub integration without building it. Your customers connect their own Google Cloud Pub/Sub account inside your product and work their topics, streams and messages there, with no per-customer code on your side.
- Handle the part that actually costs time: ordering and replay are the whole problem: a consumer that falls behind must be able to resume without losing or double-processing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Google Cloud Pub/Sub update is not your on-call problem.
- One integration serves your product and your agents. The same governed Google Cloud Pub/Sub connection powers in-product features and gives AI agents scoped, audited access, so you move events between your product and your customers' systems without either side polling without wiring it twice.
Used by these teams
Compare with
Confluent Cloud
AWS KinesisWorks well with
Google CloudOften used alongside
Tools the same teams tend to run next to Google Cloud Pub/Sub, across other categories.
Snowflake
Airtable
PostgreSQL
Anthropic ClaudeGoogle Cloud Pub/Sub integration FAQ
How do I add a Google Cloud Pub/Sub integration to my product?
Enable the Google Cloud Pub/Sub connector in your fastn dashboard, then let each customer authenticate their own Google Cloud Pub/Sub account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Google Cloud Pub/Sub client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Google Cloud Pub/Sub account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Google Cloud Pub/Sub account and only ever sees their own topics, streams and messages. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Google Cloud Pub/Sub integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent publishes a message to hand work to another system within governed permissions.
Who maintains the Google Cloud Pub/Sub integration?
fastn does. When Google Cloud Pub/Sub changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product replay Google Cloud Pub/Sub messages after an outage?
Yes, within the retention the customer's own Google Cloud Pub/Sub setup keeps. Consumer position is tracked per tenant, so a consumer that falls behind resumes from where it stopped rather than skipping ahead or starting over, which is the difference between a gap in your data and a duplicate in it.
How is one customer's stream kept separate from another's?
Each customer authorises their own Google Cloud Pub/Sub connection, so topics, credentials and consumer positions are theirs alone. That matters more here than in most integrations, because a misrouted message is delivered before anyone can review it.
What can I build with the Google Cloud Pub/Sub integration?
A common starting point: publish messages to their own topics from events in your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Google Cloud Pub/Sub integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Google Cloud Pub/Sub does not change your per-connector cost. You can start free with 3 connected accounts.
Add Google Cloud Pub/Sub to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.