Google Docs

Preview only

Google Docs configuration, OAuth connection testing, and private-document extraction are present, but extracted records are not yet written to Coyote transactions, external transactions, partners, or products. Do not rely on this integration for production imports.

What works today

• Create a Google Docs integration with a document URL or ID.
• Connect a Google account for a private document.
• Test whether the connected account can access the document.
• Extract structured content from a private document using table, template, or structured parse mode.
• Review integration run history.

Public-document connection testing can confirm that an export URL is reachable, but public HTML parsing currently returns no import records.

Safe preview setup

1. Open Admin → Integrations → Google Integrations → Google Docs.
2. Choose Private (OAuth).
3. Paste the Google Docs URL; the app extracts its document ID.
4. Save the integration, connect the Google account that can read the document, and test the connection.
5. Keep the integration disabled for production automation.
6. Use non-sensitive sample content and inspect Event History after a manual test.

The target-entity choices describe the planned destination once record processing is implemented; selecting one does not currently create those entities.

Supported alternatives

Need	Use now
Tabular data from Google Workspace	Google Sheets
TransLog, CSV, LACT, or pipeline files	Managing Imports
Dispatch tickets	LoadCall on the Integrations page
Custom HTTP delivery	Webhooks

This page should be updated only after the provider maps extracted records and persists them with the same validation/idempotency guarantees as the supported import paths.