> ## Documentation Index
> Fetch the complete documentation index at: https://docs.p2hs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Google Docs to P2HS

> Use the Google Docs connector with P2HS applications and capabilities.

## Overview

Customer-bound Google Docs (BYOC). Not P2HS-owned Drive or platform storage.

**Category:** Documents\
**Catalog status:** preview

## Supported capabilities and connector actions

| Connector action | Description |
| - | - |
| `google_docs.create_document` | Create document. Create a Google Doc in the connected customer account. |
| `google_docs.get_document` | Get document. Retrieve a Google Doc by provider document ID. |
| `google_docs.insert_text` | Insert text. Insert text at a Docs API index (defaults to 1). |
| `google_docs.append_text` | Append text. Append text at the end of the document body. |
| `google_docs.replace_all_text` | Replace all text. Replace all occurrences of a find string in the document. |

## Direction

* **P2HS → Google Docs:** Yes — supported actions can send data or requests to the provider.
* **Google Docs → P2HS:** No inbound trigger is listed in the catalog.
* **Webhooks:** No webhook or inbound event is declared in the catalog.

## Prerequisites

* A Google Docs account with permission to create or authorize the connection.
* The credentials or authorization flow required by P2HS (Oauth).
* Any provider-side account, workspace, repository, store, or sending-domain permissions required for the selected capability.

## Connect the integration

1. Open the P2HS dashboard.
2. Select the project or workspace where the connector will be used.
3. Open Integrations and choose **Google Docs**.
4. Select Connect and complete the provider authorization or credential form.
5. Save the connection and run the verification check.
6. Bind the connection to a compatible capability, App Block, or Feature Pack.

## Credentials and configuration

**Authentication:** Oauth.

The current catalog requires these credential fields:

* `access_token`
* `refresh_token`
* `client_id`
* `client_secret`

Configurable fields exposed by the connector:

* `document_id`

P2HS stores connector credentials as managed secrets. Rotate or revoke them from the connection settings; do not commit them to source code or expose them in browser code.

## Generated applications

After **Google Docs** is connected, compatible capabilities and composed application features can bind to the connection. The generated application should call the approved P2HS capability rather than embedding Google Docs credentials.

```text theme={null}
Generated application
        ↓
P2HS capability
        ↓
Google Docs connector
        ↓
External provider
```

## Events and webhooks

No inbound event is declared for this connector in the current catalog.

## Troubleshooting

* **Authentication failed:** confirm the credential or authorization flow and the provider account selected.
* **Permission denied:** verify that the provider account can access the configured resource and action.
* **Action unavailable:** confirm that the capability is admitted for the project and supported by this connector.
* **Event not received:** check the connection status, provider event configuration, and the project environment.

## Disconnect or rotate credentials

Update or revoke the connection from the project or workspace Integrations settings. Dependent capabilities may stop working after disconnecting; reconnect and verify the binding before retrying the application flow.

## Related concepts

* [Integration troubleshooting](/content/support/troubleshooting/integrations)
* [Connector model](/content/integrations/connectors)
* [App features](/content/backend/overview)
* [Capabilities reference](/content/composition/capabilities)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.