> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/data-analytics-and-bi/google-pubsub.md).

# Google PubSub

How to connect using the Google PubSub system integration

<div align="left"><figure><img src="https://391958821-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpokYqd27yrOUxIBhyvbF%2Fuploads%2Fzlf71VgYjTp1vFu6aB4c%2FScreenshot-from-2022-03-03-15-32-26-1024x467.webp?alt=media&amp;token=4a1918ae-c2f4-42cf-aa0d-c78ee903c8eb" alt=""><figcaption></figcaption></figure></div>

## Overview

Couchdrop can publish data directly to Google PubSub through Automations.

This allows files or payloads received from cloud storage, SFTP/FTP, APIs, or inbound webhooks to be sent to a Google PubSub topic as part of an automated workflow.

### How Google PubSub works with Couchdrop

Google PubSub is configured in Couchdrop as a **System Integration**.

Unlike storage connections, the integration does not appear as a Virtual Folder. Instead, the Google PubSub connection is available as a file action inside an Automation.

## How to connect to Google PubSub from Couchdrop

{% hint style="warning" %}

#### Before you start

To connect Google PubSub to Couchdrop, you will need:

* A Google Cloud account
* An existing Google PubSub topic
* Your Google Cloud **Project ID**
* Your Google PubSub **Topic Name**
  {% endhint %}

{% stepper %}
{% step %}

### Create service account credentials

In Google, navigate to **APIs & Services** > **Credentials**.

Create a service account, then create a key for that account and download the associated JSON credentials file.

You will upload this file when configuring the Google PubSub integration in Couchdrop.
{% endstep %}

{% step %}

### Create a System Integration

Log in to Couchdrop and add a new **System Integration**.

Select **Google PubSub** from the list of available integrations.
{% endstep %}

{% step %}

### Configure the Google PubSub integration

Enter the connection details for your Google PubSub topic.

| Setting                       | Description                                                                                              |
| ----------------------------- | -------------------------------------------------------------------------------------------------------- |
| **Integration name**          | Enter a name to identify the Google PubSub integration in Couchdrop.                                     |
| **Google PubSub Project ID**  | Enter the Google Cloud project ID containing the PubSub topic.                                           |
| **Google PubSub Topic Name**  | Enter the name of the PubSub topic Couchdrop will publish data to.                                       |
| **Service account JSON file** | Upload the JSON credentials file for the Google service account Couchdrop will use to connect to PubSub. |

For **Service account JSON file**, click the upload area to choose the file or drag and drop the JSON file into Couchdrop.

Click **Add System Integration** to save the connection.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/integrations/data-analytics-and-bi/google-pubsub.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.