Help Center

Docs

Integrations

Browse, connect, and manage every CRM integration from a unified hub

Open Settings > Integrations for a single hub that lists every catalog integration with a real brand logo, live connection status, and a slide-in detail panel. Search, filter by category, or click a card to connect, manage, or read about what an integration does.

Finding integrations

Where the hub lives and how to navigate it.

  • In the sidebar, click SettingsIntegrations (formerly labeled Connected Accounts — the rename ships with this redesign).
  • The hero at the top shows totals: how many integrations are connected, how many are available, and how many are reporting errors. Click a tile to filter the grid to that status.
  • Use the search box to filter by name, description, or category. Combine search with one or more category pills (Automation, Calling & SMS, etc.) to narrow further. Filters are reflected in the URL, so you can share a filtered view with a teammate.
  • Deep-link to a specific integration with ?integration=<id> (e.g. /settings/integrations?integration=docusign) — the drawer opens on page load.

Connecting an integration

Click a card to open the drawer, then click Connect.

1

Open the integration drawer

Click any card in the grid. A slide-in panel opens on the right with the integration's name, description, and current status.
2

Review what you&apos;re authorizing

The drawer summarizes what the integration does. For OAuth providers (Google, Microsoft, Mailchimp, etc.), Laureo redirects you to the provider for explicit scope consent. For API-key providers, you'll paste a key on the per-provider settings page.
3

Click Connect (or Configure)

OAuth providers redirect you to the third-party consent screen. Webhook providers (Slack, Make, Zapier, Typeform, Jotform) take you to the per-provider page to copy a generated webhook URL or paste a token. After consent, you're returned to the hub with the card updated to Connected.
Manage advanced settings is one click away
Once connected, the drawer offers Manage advanced settings → to take you to the per-provider configuration page where you can adjust field mappings, webhook secrets, sync windows, or disconnect.

Per-user vs org-wide integrations

Some integrations are personal; most affect the whole organization.

Every catalog card carries an installation scope— visible in the drawer's header subtitle:

  • Per-user integrations(4 entries) bind to your personal OAuth token. Each seat connects their own — there's no shared org-level credential. The drawer renders the connect / disconnect / sync UI inline so you never leave the hub. The per-user catalog is: Google Workspace, Microsoft 365, Google Drive (piggybacks on the Google Workspace token), and OneDrive (piggybacks on Microsoft 365).
  • Org-wide integrations(28 entries) are organization-level. One admin connects, and every seat sees the integration as “Connected” on the hub. Examples: Mailchimp, Twilio, DocuSign, QuickBooks, Slack, Zapier, Calendly. Connecting one of these is gated by the integrations.connect permission.
Google Drive and OneDrive are not separate connections
Drive and OneDrive piggyback on the Google Workspace and Microsoft 365 OAuth tokens respectively. Clicking either card opens a drawer that explains the piggyback and lets you manage the parent connection. Disconnecting Google Workspace also stops Drive access; same for Microsoft 365 and OneDrive.

Status indicators

What each badge means.

  • Connected (green dot) — the integration is active and syncing.
  • Available (no badge) — the integration is in the catalog but not yet set up.
  • Error (amber dot) — Laureo last hit an error talking to the provider. The drawer shows the last error message; reconnecting usually clears it.
  • Beta — the integration is shipping in preview. It works, but expect rough edges.
  • Coming Soon (grayed) — on the roadmap, not yet wired up. Cards in this state are non-clickable.

Disconnecting

Per-user: from the drawer. Org-wide: from the per-provider page.

For per-user integrations (Google Workspace, Microsoft 365, Google Drive, OneDrive) the Disconnect button is built into the drawer — confirm the action and the connection ends immediately. Already-synced data (email metadata, calendar event metadata, linked-file references) is purged from Laureo, but your actual emails, calendar, and files stay on the provider side.

For org-wide integrations the drawer hands off to the per-provider settings page via the Manage advanced settings →link — that's where the disconnect / remove-credentials button lives. Each provider has its own cleanup nuances (e.g., DocuSign tears down envelope webhooks, Slack stops broadcasts but keeps the channel mapping for one re-connection cycle).

Permission requirements

Who can connect, configure, or disconnect each integration.

  • integrations.connect — gates the Connectbutton on org-wide cards. Without it, the button is disabled and a tooltip explains you need to ask an admin. Per-user cards (Google Workspace, Microsoft 365, Drive, OneDrive) bypass this — each seat can always connect their own account.
  • integrations.configure — gates the Manage advanced settings → link and the Disconnectbutton on org-wide cards. Required to change credentials, webhook secrets, field mappings, or to disconnect an org-wide integration.
  • messaging.send_sms / messaging.send_voice / messaging.send_whatsapp — per-seat permission to actually useTwilio / WhatsApp for outbound messaging on entity pages. Connecting Twilio is a one-time admin action; sending happens under each seat's messaging permission.
  • documents.send — per-seat permission to send an envelope through DocuSign or PandaDoc.
  • sync.trigger— per-seat permission to fire the manual “Sync now” button on the per-provider settings pages.
Roles set defaults; admins override per user
Built-in roles ship with sensible defaults — super_admin and admin have all five gates, sales_manager has messaging.send_* + documents.send + sync.trigger but not the org-level integrations.* gates, and sales_rep / marketing / service have none of the org-level connect / configure gates by default. Override any of them per role on Admin > Roles & Permissions.

Google Workspace (Gmail, Calendar, Drive, Meet)

Per-user OAuth covering email push sync, two-way calendar sync, scope-minimized Drive access, and Meet transcript auto-link.

What syncs

  • Gmail — Send, sync, archive, trash, and reply from the CRM. Email threads are linked to contact and company records automatically. Sync is real-time via push notifications — new mail typically appears in the CRM within seconds of arriving in your Gmail inbox.
  • Google Calendar — Two-way sync of events with attendees and reminders. Activities scheduled in the CRM appear on your Google Calendar and vice versa.
  • Google Drive — Browse and attach files using Google's native file picker. The CRM only sees the specific files you choose.
  • Google Meet — Auto-link Meet transcripts and recordings to CRM activity records (requires the Meet recording scope granted at connect time).
Scope-minimized Drive access
For Google Drive, the CRM uses the Google Picker API together with the non-sensitive drive.filescope. You browse your Drive inside Google's own picker UI, and the CRM only gains access to the specific files you select — never your full Drive. This is the pattern Google recommends for minimizing OAuth scope exposure.
Auto-link Meet transcripts and recordings
After connecting Google, enable Auto-link Meet transcripts in the Google Workspace drawer. Transcripts and recordings saved to your Drive by Google Meet are automatically linked to the matching CRM activity — no manual attach step. See Meet Transcripts for details. Google Meet transcripts are a paid Google Workspace feature; personal Gmail accounts can't generate them.
Reconnect Google if you connected before April 2026
If your Google connection was made before the upgrade to real-time push sync and the scope-minimized Drive Picker flow, your token still holds older, broader permissions and isn't subscribed to push notifications. Open the Google Workspace drawer, click Disconnect, then click Connect again to receive the new scopes and enable real-time email sync. Your previously synced data and linked files are preserved.

Microsoft 365 (Outlook, Calendar, OneDrive, To Do, Teams)

Per-user OAuth covering mail, calendar, contacts, tasks, OneDrive files, Teams meeting links, and out-of-office indicators.

What syncs

  • Outlook Mail — real-time push sync via Microsoft Graph subscriptions on /me/messages. Send, archive, trash, reply.
  • Outlook Calendar — two-way sync with delta queries, lifecycle webhooks for self-healing.
  • Outlook Contacts — bidirectional contact sync with auto-import to People.
  • Microsoft To Do — opt-in bidirectional task sync.
  • Microsoft Teams — generate Teams join links on calendar invites (business accounts only — personal Microsoft accounts can't use the standalone Teams API).
  • OneDrive — browse and link files to CRM records.
  • SharePoint — browse and link site documents (requires tenant admin consent).
  • Out-of-Office — surface OOF replies on contact panels.

Microsoft Teams channel broadcasts (Deal Won, New Lead, etc.) are configured separately on the Microsoft Teams integration card — see below.

Slack & Microsoft Teams broadcasts

Org-channel notifications powered by an incoming webhook URL.

Configure a Slack incoming webhook or a Microsoft Teams workflow URL on the corresponding integration card, then toggle on the events your team wants broadcast. Ten CRM event types are supported:

  • Deal Won — a deal is marked as won
  • Deal Lost — a deal is marked as lost
  • Pipeline Stage Change — a deal advances or retreats
  • New Lead — a lead enters the CRM
  • New Contact — a person record is created
  • Task Overdue — a task passes its due date unresolved
  • Ticket Created — a new support ticket is filed
  • Invoice Paid — an invoice payment is recorded
  • Quote Accepted — a customer accepts a quote
  • Meeting Scheduled — a meeting activity is created
Org-channel vs. personal notifications
Slack and Teams broadcasts are org-level— they post to your team channel regardless of who performed the action. They're separate from per-user notifications (bell, inbox, email, browser push) which are governed by each user's own preferences on Settings > Notifications.

WordPress (per-site tracking keys + HMAC)

Capture page views from your WordPress site as CRM activities — securely.

The WordPress integration is configured under a dedicated settings page at Settings > Integrations > WordPress. Each WordPress site you want to track registers separately and receives its own tracking key + HMAC secret. Events are signed on your WordPress server with an HMAC secret that never leaves the server — visitors cannot read it from page source.

See WordPress integration for the full step-by-step registration and plugin install guide.

The old WordPress script tag is no longer accepted
An earlier version of the WordPress integration asked you to paste an organization-wide API key directly into a <script> tag on your WordPress page. That approach exposed the key to anyone viewing the page source. The v2 integration replaces it with site-scoped tracking keys + a server-side HMAC secret. If you had the old script tag installed, register each site under the new flow.

Email Verification (sending-domain DNS)

SPF, DKIM, and DMARC for reliable outbound email delivery.

Configure domain verification to improve email deliverability and establish trust with email providers. The following DNS records must be configured:

  • SPF — Sender Policy Framework — authorizes Laureo to send emails on behalf of your domain.
  • DKIM — DomainKeys Identified Mail — adds a digital signature to outgoing emails for authentication.
  • DMARC — Domain-based Message Authentication, Reporting, and Conformance — tells receiving servers how to handle unauthenticated emails.
DNS changes may take time
After adding SPF, DKIM, and DMARC records to your domain's DNS settings, it can take up to 48 hours for changes to propagate. The CRM will periodically re-check your domain verification status.