integrations

Open Integrations in dripos to connect the sources you want. You do not need to connect everything, and each source keeps its own permissions and review rules.

recommended setup

Start with the sources where your customer conversations already happen:

iMessage for texts.
Google for Gmail and Calendar.
Slack for workspace messages.
LinkedIn if you use LinkedIn DMs with customers.
Stripe if you want revenue signals on people and companies.

Meeting and scheduling tools can be added later.

availability

The current Integrations screen exposes these first-class cards:

iMessage
Google
Slack
LinkedIn
Stripe
Granola
Circleback
Cal.com
Calendly

Some older or secondary source surfaces still have backend or local plumbing, but are not normal first-class Integrations cards in the current Mac app: Fathom, Pocket AI, and Google Messages. Use them only when your build exposes an explicit control for that source. Lead import setup lives in Leads, not Integrations, but it uses the same source model as imported lead files.

sources

source	what it adds	what you may be asked for
iMessage	local Messages history and approved text sends	Full Disk Access, then Messages automation
Google	Gmail threads and Calendar meetings	Google sign-in and consent
Slack	workspace messages, DMs, shared channels, and reply drafts	Slack workspace consent
Stripe	customer and revenue signals	Stripe Connect consent
LinkedIn	local-bridge DMs, group chats, media, history import, and drafts	LinkedIn login in a browser window
Lead import	imported leads from a CRM, enrichment tool, form, or automation	a copied endpoint, header, and JSON body
Granola	AI meeting notes, transcripts, and attendees	Granola MCP OAuth
Circleback	meetings, transcripts, calendar, email, and action items	Circleback MCP OAuth
Cal.com	scheduling context for reviewed booking actions	Cal.com MCP OAuth
Calendly	scheduling context for reviewed booking actions	Calendly MCP OAuth

Lead import

Use lead import when another tool already has the people you want to bring into dripos. This can be a CRM, an enrichment table, a form tool, a website event, Zapier, Make, or any tool that can send data to another app.

Open Leads in dripos.
Click Set up lead import.
dripos copies the endpoint, Authorization header, and JSON body.
In the tool that has your leads, add an automation that sends lead data to another app. It might be called a webhook, HTTP request, or POST action.
Choose POST, set Content-Type: application/json, and paste the copied values.
Send one test lead.
Return to dripos and click Import leads.

A lead needs a name to appear in dripos. To make outreach useful, include at least one reachable channel such as email, phone, or linkedinUrl.

{
  "leads": [
    {
      "externalId": "crm-contact-123",
      "name": "Ava Founder",
      "company": "Finch Pay",
      "email": "ava@finch.test",
      "linkedinUrl": "https://linkedin.com/in/ava",
      "painSignal": "visited pricing page twice"
    }
  ]
}

Importing leads does not send messages by itself. Outreach still follows your dripos review and AutoSend settings.

LinkedIn opens a browser login window. Sign in there, then return to dripos. When a valid LinkedIn bridge session exists, dripos can run realtime updates and explicit Sync LinkedIn catchups. Import history pulls older pages conservatively when LinkedIn allows it. If LinkedIn shows Cooling down, leave it alone and try again later. Repeated reconnect attempts can make throttling worse. If LinkedIn shows local bridge session is missing, reconnect LinkedIn from Integrations. That message means dripos cannot read the browser bridge session needed for sync or send. dripos does not background-crawl LinkedIn profile pictures. The app uses participant names, initials, source handles, profile URLs when already available, and local contact metadata first.

group conversations

dripos surfaces group conversations separately from person threads. Supported group surfaces include:

Slack channels
Slack threads
iMessage groups
LinkedIn group chats

The group row can show participant count, member names, related people, related company, match reasons, and whether there is unreplied inbound activity. Timeline attribution uses sender metadata when available and conservative inference for older LinkedIn rows.

sync

Click Sync all after connecting sources. The first sync may take a few minutes. Sync all runs supported native sync targets such as iMessage, Gmail, Slack, LinkedIn when the bridge is connected, Granola, Circleback, Cal.com, and Calendly. Some rows have special behavior:

Stripe is a hosted connection and contributes revenue signals.
LinkedIn uses explicit sync and history import controls to stay conservative.
Fathom, Pocket AI, and Google Messages are secondary or legacy surfaces in the current app and are not part of the normal Sync all path unless a build exposes explicit controls for them.

You can keep using the app while sync runs.

disconnect

Open Integrations, choose the source, then click Disconnect. Disconnecting stops new sync for that source. Local history already synced on your Mac may remain until local app data is removed.

​integrations

​recommended setup

​availability

​sources

​Lead import

​LinkedIn

​group conversations

​sync

​disconnect