API Integration with GW Apps & Make
Overview Make can connect a GW Apps workflow or trigger to other services. A common two-way pattern sends a GW...
Integrations
-
-
BigQuery Integration
The BigQuery Integration feature allows you to view and report on your GW Apps data directly in Google BigQuery —... -
Document Signing Action – DocuSign Integration
Overview The Document Signing action sends one or more documents from a GW Apps record to DocuSign for electronic signature.... -
BigQuery: Rotate a Service Account Key and Export Field Codes
Overview This article covers two related administration tools: changing the service account file used by an existing BigQuery dataset connection,... -
Integrations: Native Google Integration
Overview GW Apps includes a native Google integration. It allows you to use supported Google Drive, Google Docs, Google Sheets,... -
Active Directory Sync
Overview Active Directory Sync is an optional GW Apps platform feature that keeps platform accounts aligned with an external directory.... -
Database Connect: MySQL and MS SQL
Overview Database Connect allows an application to connect to an external MySQL or Microsoft SQL Server database. The connector stores...
Need Support?Contact Support
We've detected you might be speaking a different language. Do you want to change to:
English English 
Spanish
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.
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.
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.
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.