Appearance
Google Cloud Pub/Sub
Publish and subscribe to real-time messaging with Google Cloud Pub/Sub.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://pubsub.googleapis.com/v1 |
| Authentication | See connector docs |
| Endpoints | 8 |
| Connector key | gcp-pubsub |
Using Google Cloud Pub/Sub in a workflow
- Go to Connections and click New Connection.
- Pick Google Cloud Pub/Sub from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /projects/{project}/topics | List topics |
PUT /projects/{project}/topics/{topic} | Create a topic |
DELETE /projects/{project}/topics/{topic} | Delete a topic |
POST /projects/{project}/topics/{topic}:publish | Publish messages |
GET /projects/{project}/subscriptions | List subscriptions |
PUT /projects/{project}/subscriptions/{subscription} | Create a subscription |
POST /projects/{project}/subscriptions/{subscription}:pull | Pull messages |
POST /projects/{project}/subscriptions/{subscription}:acknowledge | Acknowledge messages |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /projects/{project}/topics
List topics
| Detail | Value |
|---|---|
| Operation ID | cloud.listTopics |
| Method | GET |
| Path | /projects/{project}/topics |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listTopics. - 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
| Detail | Value |
|---|---|
| Operation ID | cloud.createTopic |
| Method | PUT |
| Path | /projects/{project}/topics/{topic} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createTopic. - 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
| Detail | Value |
|---|---|
| Operation ID | cloud.deleteTopic |
| Method | DELETE |
| Path | /projects/{project}/topics/{topic} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.deleteTopic. - 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
| Detail | Value |
|---|---|
| Operation ID | cloud.publishMessages |
| Method | POST |
| Path | /projects/{project}/topics/{topic}:publish |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.publishMessages. - 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
| Detail | Value |
|---|---|
| Operation ID | cloud.listSubscriptions |
| Method | GET |
| Path | /projects/{project}/subscriptions |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listSubscriptions. - 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
| Detail | Value |
|---|---|
| Operation ID | cloud.createSubscription |
| Method | PUT |
| Path | /projects/{project}/subscriptions/{subscription} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createSubscription. - 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
| Detail | Value |
|---|---|
| Operation ID | cloud.pullMessages |
| Method | POST |
| Path | /projects/{project}/subscriptions/{subscription}:pull |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.pullMessages. - 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
| Detail | Value |
|---|---|
| Operation ID | cloud.acknowledgeMessages |
| Method | POST |
| Path | /projects/{project}/subscriptions/{subscription}:acknowledge |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Cloud Pub/Sub connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.acknowledgeMessages. - 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.