Skip to content

Integrations Overview

Integrations connect Sprigr Teams to the tools your organisation already uses — email, file storage, project management, customer support, cloud infrastructure, and more. Once connected, your agents can read data from and take actions in those external systems as part of their conversations and workflows.

Integration Hub

Each integration follows the same pattern:

  1. Connect — An admin authorises Sprigr Teams to access the external service. Depending on the integration, this is done via OAuth (you sign in and grant permissions), an API key, or a service account.
  2. Assign — You assign the integration to specific agents or make it available to all agents in your organisation.
  3. Use — Agents automatically discover their available integrations and use them when relevant. For example, if a customer asks about an order, an agent with the Gorgias integration can look up the ticket without being told how.

All credentials are encrypted and stored securely within your organisation’s workspace. Sprigr Teams never shares your credentials across organisations.

When you connect an integration, you choose its scope:

  • Company-wide — Every agent in your organisation can use the integration. This is the simplest option and works well for widely-used tools like email and file storage.
  • Agent-specific — Only selected agents can use the integration. Use this when you want to limit which agents have access to sensitive systems. For example, you might restrict your AWS integration to only your DevOps Agent.

You can change the scope at any time from the integration settings.

The Integration Hub is your central place for managing all connections. Access it from the sidebar by clicking Integrations. The Hub has two tabs:

This tab shows all external service connections. Each integration card displays:

  • The service name and logo
  • Connection status (connected, disconnected, or error)
  • Which agents have access
  • When it was last used

Click any integration to view its settings, update credentials, or change the scope.

Skills are pre-built capabilities that agents can use without connecting to an external service. They include things like web search, calculations, and data formatting. Skills are managed separately from integrations because they do not require authentication.

Sprigr Teams includes integrations for the following services:

Gmail

Read, send, and manage emails through Google Workspace. Search mailboxes, send replies, and manage labels. Set up Gmail

Outlook

Access email and calendar through Microsoft 365. Read and send mail, list and create calendar events. Set up Outlook

Google Drive

Search, read, and upload files in your organisation’s Google Drive. Reference documents in conversations. Set up Google Drive

GitHub

Access repositories, issues, pull requests, branches, and code. Create comments and manage issues. Set up GitHub

Gorgias

Read and manage customer support tickets. View customer details, add notes, and respond to messages. Set up Gorgias

simPRO

Access jobs, quotes, schedules, customers, and more from your simPRO field service management platform. Set up simPRO

AWS

Query and manage your Amazon Web Services infrastructure including compute, storage, and monitoring. Set up AWS

GCP

Query and manage your Google Cloud Platform resources including compute, storage, and monitoring. Set up GCP

Most integrations use OAuth for authentication. Here is what the process looks like:

  1. Click “Connect” on the integration card in the Hub
  2. Sign in to the external service in the popup window that appears
  3. Grant permissions — review what Sprigr Teams is requesting access to and click “Allow” or “Authorise”
  4. Return to Sprigr Teams — the popup closes and the integration shows as connected

The OAuth flow is a one-time setup per integration. Sprigr Teams securely stores the access tokens and refreshes them automatically, so you do not need to re-authenticate unless you revoke access from the external service.

Sprigr Teams takes integration security seriously:

  • Per-organisation authentication — Each organisation has its own set of integration credentials. Credentials are never shared between organisations.
  • Encrypted storage — All OAuth tokens, API keys, and service account credentials are encrypted at rest.
  • Scoped access — You control which agents can use each integration, limiting the blast radius if something goes wrong.
  • Audit logging — Every action an agent takes through an integration is logged so you can review what happened and when.
  • Gmail — Connect Google Workspace email to your agents.
  • Outlook — Connect Microsoft 365 email and calendar.
  • Agent Settings — Assign integrations to specific agents.
  • Workflows — Use integrations inside automated workflows.