Connect GW Apps with external systems through APIs, webhooks, automation platforms, databases, signing services, and built-in integrations.

Overview

GW Apps can connect application data and processes with Google Workspace,
Microsoft services, automation platforms, databases, signing services,
and other systems. The available connection method depends on the task:
some capabilities are built into GW Apps, while others use the GW Apps
API, webhooks, or an automation platform such as Make or Zapier.

Use this page to choose the appropriate integration path and open the
detailed setup article. Availability may depend on your GW Apps plan,
enabled platform features, and the third-party account or license used
by your organization.

Before You Begin

Confirm that you have the required GW Apps role. App-level
integrations normally require App Designer access; platform API
keys and platform-wide settings require Super Administrator access.
Confirm that the external account is active and that you can grant
the permissions requested by that service.
Use a dedicated integration identity where practical, and grant only
the GW Apps scopes and third-party permissions required for the
workflow.
Check current plan availability and organization policies before
designing a production integration.

Built-In Google Workspace Capabilities

When a user connects an eligible Google account, GW Apps can use that
authorized connection in supported Google features. The first use may
require the user to sign in, review the requested permissions, and grant
access.

Native Google IntegrationNative Google integration allows you to use supported Google Drive, Google Docs, Google Sheets, and Google Calendar features directly from GW Apps.

Drive Picker fieldSelect files from Google Drive from a GW Apps form.

Actions reference: Google Calendar eventCreate a Google Calendar event from an action used in a workflow or trigger.

Additional Google Workspace actions, including Google document or
spreadsheet creation where enabled, should be documented on their
individual action pages and linked from this index.

GW Apps API and Webhooks

Use the GW Apps REST API when another system needs to read or change
GW Apps data. Use a webhook action when GW Apps needs to send record
or workflow information to an external endpoint. These methods can be
combined in a two-way integration.

API documentationBrowse GW Apps API configuration and endpoint guidance.

GW Apps Records APIGenerate a bearer token and work with application records.

Platform: API KeysCreate credentials for platform-level Users and Shared Roles APIs.

Automation Platforms

Automation platforms can receive GW Apps webhooks, transform data,
call the GW Apps API, and connect GW Apps with services that are not
configured directly in the application.

API Integration with GW Apps & MakeBuild a webhook-to-API scenario using Make.

Zapier can be used for comparable automation patterns when a suitable
trigger, webhook, or API step is available. Follow current Zapier
documentation for its configuration and use the GW Apps API documentation
for GW Apps authentication, identifiers, scopes, and payloads.

Data and Service Integrations

BigQuery IntegrationConnect GW Apps to Google BigQuery where the feature is enabled.

Document Signing Action — DocuSign IntegrationSend supported documents through a DocuSign action.

GW Apps also supports integration patterns involving MySQL and Microsoft
SQL Server. Confirm the current enablement, prerequisites, and supported
configuration with GW Apps before planning a production database
connection.

Microsoft 365, Teams, and Slack

GW Apps product information identifies Microsoft 365, Microsoft Teams,
and Slack among the services that can be used with GW Apps. The exact
implementation may be a built-in capability, notification pattern, API,
webhook, or automation-platform workflow.

Choosing an Integration Method

Use the table below to identify the integration approach that best matches
what your application needs to do.

Integration method	When to use it
Built-in capability	Use when GW Apps provides the field or action directly, such as Drive Picker or a Google Calendar event action.
Webhook	Use when a GW Apps event must send data to an external endpoint or automation workflow.
GW Apps API	Use when an external process must authenticate and read or change GW Apps data.
Make or Zapier	Use when a visual automation service is needed to route data, transform values, or connect multiple services.
Database or service integration	Use the dedicated integration article and confirm feature availability, credentials, networking, permissions, and the support boundary.

Security and Support Boundaries

Keep API keys, access tokens, connection credentials, and webhook
secrets out of documents, screenshots, logs, and shared messages.
Restrict credentials to specific users, forms, entities, and scopes
whenever the integration supports those controls.
Test with non-production data before enabling a workflow or trigger
in a live application.
GW Apps documentation governs the GW Apps configuration. The external
provider’s documentation governs its authentication, limits,
retention, licensing, and service behavior.
For an incident, disable the affected key or connection, rotate
exposed credentials, and review both GW Apps and external-service
logs.

AI & Integrations

Integrations

AI Features

Recommended learning path

Explore built-in AI features

Configure AI and agent capabilities

Connect external systems

Browse AI and integration topics

Knowledge Base