Skip to content
For LLMsView as Markdown·

Google Cloud Pub/Sub

Publish and subscribe to real-time messaging with Google Cloud Pub/Sub.

DetailValue
CategoryCloud & Infra
Base URLhttps://pubsub.googleapis.com/v1
AuthenticationSee connector docs
Endpoints8
Connector keygcp-pubsub

Using Google Cloud Pub/Sub in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Google Cloud Pub/Sub from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET /projects/{project}/topicsList topics
PUT /projects/{project}/topics/{topic}Create a topic
DELETE /projects/{project}/topics/{topic}Delete a topic
POST /projects/{project}/topics/{topic}:publishPublish messages
GET /projects/{project}/subscriptionsList subscriptions
PUT /projects/{project}/subscriptions/{subscription}Create a subscription
POST /projects/{project}/subscriptions/{subscription}:pullPull messages
POST /projects/{project}/subscriptions/{subscription}:acknowledgeAcknowledge messages

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /projects/{project}/topics

List topics

DetailValue
Operation IDcloud.listTopics
MethodGET
Path/projects/{project}/topics

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.listTopics.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.

PUT /projects/{project}/topics/{topic}

Create a topic

DetailValue
Operation IDcloud.createTopic
MethodPUT
Path/projects/{project}/topics/{topic}

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.createTopic.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.

DELETE /projects/{project}/topics/{topic}

Delete a topic

DetailValue
Operation IDcloud.deleteTopic
MethodDELETE
Path/projects/{project}/topics/{topic}

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.deleteTopic.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.

POST /projects/{project}/topics/{topic}:publish

Publish messages

DetailValue
Operation IDcloud.publishMessages
MethodPOST
Path/projects/{project}/topics/{topic}:publish

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.publishMessages.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.

GET /projects/{project}/subscriptions

List subscriptions

DetailValue
Operation IDcloud.listSubscriptions
MethodGET
Path/projects/{project}/subscriptions

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.listSubscriptions.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.

PUT /projects/{project}/subscriptions/{subscription}

Create a subscription

DetailValue
Operation IDcloud.createSubscription
MethodPUT
Path/projects/{project}/subscriptions/{subscription}

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.createSubscription.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.

POST /projects/{project}/subscriptions/{subscription}:pull

Pull messages

DetailValue
Operation IDcloud.pullMessages
MethodPOST
Path/projects/{project}/subscriptions/{subscription}:pull

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.pullMessages.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.

POST /projects/{project}/subscriptions/{subscription}:acknowledge

Acknowledge messages

DetailValue
Operation IDcloud.acknowledgeMessages
MethodPOST
Path/projects/{project}/subscriptions/{subscription}:acknowledge

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
  3. In the Operation dropdown, select cloud.acknowledgeMessages.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Pub/Sub API reference.