Integration

Google Pub/Sub integration

Google Cloud Pub/Sub messaging service API for reliable, scalable, asynchronous messaging between services. Create topics and subscriptions, publish and pull messages, manage schemas, and configure push delivery endpoints.

Connect Google Pub/Sub How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Google Pub/Sub.Built from the 23 Google Pub/Sub tools below, on the connection you add once.

Common Google Pub/Sub use cases

automate topic management
automate subscription management
automate schema management
automate snapshot management
get topic programmatically
get schema programmatically
list topic programmatically
list schema programmatically
create topic programmatically
delete topic programmatically

What you can do with Google Pub/Sub

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Subscription, 5 operations

create_subscriptionCreate subscriptionPUTCreates a new subscription to a given topic. If the subscription already exists, returns ALREADY_EXISTS
delete_subscriptionDelete subscriptionDELETEDeletes an existing subscription. All pending messages in the subscription are immediately dropped
get_subscriptionGet subscriptionGETGets the configuration details of a subscription
list_subscriptionsList subscriptionsGETLists matching subscriptions in the given project
update_subscriptionUpdate subscriptionPATCHUpdates an existing subscription. Only the fields set in the request body are updated

Topic, 5 operations

create_topicCreate topicPUTCreates a new topic with the given name
delete_topicDelete topicDELETEDeletes the topic with the given name. Existing subscriptions are not deleted but their topic field is set to _deleted-topic_
get_topicGet topicGETGets the configuration of a topic
list_topicsList topicsGETLists matching topics in the given project
update_topicUpdate topicPATCHUpdates an existing topic. Only the fields set in the updateMask are modified

Schema, 4 operations

create_schemaCreate schemaPOSTCreates a new schema in the given project for validating published messages
delete_schemaDelete schemaDELETEDeletes a schema by name. All schema revisions are deleted as well
get_schemaGet schemaGETGets a schema by name. Get schema.
list_schemasList schemasGETLists schemas in the given project

Snapshot, 3 operations

create_snapshotCreate snapshotPUTCreates a snapshot from the requested subscription. Snapshots are used in seek operations to restore subscription state
delete_snapshotDelete snapshotDELETERemoves an existing snapshot. Snapshots are used in seek operations
list_snapshotsList snapshotsGETLists the existing snapshots in the given project

Ack deadline, 1 operation

modify_ack_deadlineModify ack deadlinePOSTModifies the ack deadline for specific messages. Useful to indicate that more time is needed to process a message

Acknowledge message, 1 operation

acknowledge_messagesAcknowledge messagesPOSTAcknowledges messages that have been pulled so they will not be delivered again

Message, 1 operation

publish_messagesPublish messagesPOSTPublishes one or more messages to a topic. Returns message IDs for each published message

Pull message, 1 operation

pull_messagesPull messagesPOSTPulls messages from the server. Returns an empty list if there are no messages available

Seek subscription, 1 operation

seek_subscriptionSeek subscriptionPOSTSeeks a subscription to a given point in time or to a snapshot, causing messages to be redelivered or acknowledged in bulk

Topic subscription, 1 operation

list_topic_subscriptionsList topic subscriptionsGETLists the names of subscriptions attached to the specified topic

OAuth scopes Google Pub/Sub requires

Each operation declares the scopes Google Pub/Sub requires for it.

https://www.googleapis.com/auth/pubsubneeded by acknowledge_messages, create_schema, create_snapshot and 20 more

Use Google Pub/Sub from Claude Code, Cursor or Codex

Connect Google Pub/Sub in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Pub/Sub operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Pub/Sub

Create your workspace
Sign up free. Nothing to install.
Connect Google Pub/Sub once
Add your Google Pub/Sub connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Pub/Sub integration FAQ

What can you do with the Google Pub/Sub integration?

LiveContext exposes 23 operations on Google Pub/Sub, covering subscription, topic, schema and snapshot. Common uses include automate topic management, automate subscription management and automate schema management.

Which OAuth scopes does Google Pub/Sub require?

The operations that declare a scope all need https://www.googleapis.com/auth/pubsub.