> ## Documentation Index
> Fetch the complete documentation index at: https://docs.newport.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Integrations: Connect Google With Your Favorite Tools
> Connect Google with Slack, GitHub, Google Workspace, Zapier, and more to automate workflows, sync data, and eliminate manual work across your stack.
Google is built to work alongside the tools your team already uses every day. Instead of asking you to replace your existing stack, the integrations layer connects Google to services like Slack, GitHub, Google Workspace, and Zapier so that data flows automatically, notifications reach the right people in the right place, and repetitive manual steps get eliminated. Every integration is set up through a straightforward authorization flow and can be managed, paused, or removed at any time from your settings panel.
## Available Integrations
Send notifications, receive alerts, and trigger actions in Google directly from Slack channels and slash commands.
Sync repositories, link issues to projects, and track code activity alongside your workspace records.
Connect your Google Calendar, Drive, and Gmail to surface relevant files and events inside Google.
Build no-code automation workflows that connect Google to hundreds of other apps through Zapier's trigger-and-action model.
Send real-time HTTP event payloads from Google to any external URL for custom integrations and event-driven automation.
Use the Google REST API to build fully custom integrations, automate data pipelines, and embed platform functionality into your own products.
## Connecting an Integration
Setting up a new integration takes just a few minutes. Follow these steps to connect any app from the integrations catalog.
Open the main navigation menu and click **Settings**. In the left sidebar of the settings panel, select **Integrations** to open the integrations management page.
Scroll through the available integrations or use the search bar to find the tool you want to connect. Each catalog entry shows a brief description, the permissions it requires, and the current connection status for your workspace.
Click the **Connect** button on the integration tile. A configuration panel slides open with instructions specific to that integration, including any API keys or OAuth scopes required.
For OAuth-based integrations (such as Slack, GitHub, and Google Workspace), you'll be redirected to the provider's authorization screen. Sign in with the account you want to connect and grant the requested permissions. You'll be returned to Google automatically once authorization is complete.
After authorization, the integration configuration panel will present options specific to that service — for example, which Slack channel to send notifications to, which GitHub repository to sync, or which Zapier triggers to enable. Complete these settings and click **Save** to activate the integration.
Slack Integration
The Slack integration keeps your team informed without requiring anyone to stay logged into Google all day. Once connected, Google can post notifications directly to any Slack channel you choose.
**What the Slack integration does:**
* Posts real-time alerts to designated channels when workspace events occur — such as a new project being created, a record reaching a specific status, or an automation run failing.
* Lets you configure per-event notification routing, so high-priority alerts go to a critical channel while routine updates go to a general channel.
* Exposes a set of **slash commands** inside Slack that let users query workspace data and take actions without leaving Slack:
* `/google search [query]` — Run a workspace search and see results in Slack.
* `/google status` — View the current workspace activity summary.
* `/google create [project name]` — Create a new project directly from Slack.
**Configuring the Slack integration:**
1. After connecting (see steps above), select the default channel where notifications should be sent.
2. Under **Notification Rules**, click **Add Rule** to map specific event types to specific channels or users.
3. Toggle individual notification categories on or off — such as project events, record changes, or integration errors — to control the volume of messages.
4. Click **Save** to apply your configuration. You can return to this panel at any time to adjust your settings.
GitHub Integration
The GitHub integration bridges your development workflow and your Google workspace, keeping code activity and project tracking in sync.
**What the GitHub integration syncs:**
* **Repositories** — Link one or more GitHub repositories to Google projects, so commits, pull requests, and issues appear in your workspace Activity Feed.
* **Issues** — Automatically create or update Google records when GitHub issues are opened, closed, or labeled.
* **Pull Requests** — Surface PR status in related Google records so project stakeholders can see development progress without needing a GitHub account.
* **Commit References** — When a commit message references a Google record ID, the commit is linked to that record's timeline.
**Connecting your repository:**
1. In the GitHub integration settings, click **Add Repository**.
2. Authorize Google's GitHub App on your GitHub account or organization (you'll need admin rights on the repository).
3. Select the specific repositories you want to sync from the dropdown list.
4. Choose which event types (issues, pull requests, commits, releases) should generate activity in Google.
5. Click **Save**. The integration will perform an initial sync and then stay up to date in real time via GitHub webhooks.
## Managing Connected Apps
All of your connected integrations are visible in **Settings > Integrations > Connected Apps**. From this panel you can:
* **View status** — See whether each integration is active, paused, or in an error state, along with the last time it successfully synced.
* **Reconfigure** — Click **Edit** on any integration to adjust its sync settings, notification rules, or authorized scopes without disconnecting it.
* **Pause** — Toggle the integration off temporarily to stop syncing and notifications without revoking the underlying authorization. Useful during testing or maintenance windows.
* **Disconnect** — Click **Disconnect** to fully remove the integration and revoke Google's access to the connected service.
Disconnecting an integration immediately revokes Google's access token for that service. Any automation rules, notification routes, or sync configurations tied to that integration will stop working. Data that was already synced to your workspace is not deleted, but no new data will flow in or out. If you reconnect the integration later, you will need to reauthorize and reconfigure it from scratch. If you only need a temporary pause, use the **Pause** toggle instead of disconnecting.