Skip to main content

​
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. Start with the sources where your customer conversations already happen:
  1. iMessage for texts.
  2. Google for Gmail and Calendar.
  3. Slack for workspace messages.
  4. LinkedIn if you use LinkedIn DMs with customers.
  5. Stripe if you want revenue signals on people and companies.
Meeting and scheduling tools can be added later.

​
sources

sourcewhat it addswhat you may be asked for
iMessagelocal Messages history and approved text sendsFull Disk Access, then Messages automation
GoogleGmail threads and Calendar meetingsGoogle sign-in and consent
Slackworkspace messages, DMs, shared channels, and reply draftsSlack workspace consent
Stripecustomer and revenue signalsStripe Connect consent
LinkedInlocal-bridge DMs, group chats, media, history import, and draftsLinkedIn login in a browser window
GranolaAI meeting notes, transcripts, and attendeesGranola MCP OAuth
Fathommeeting summaries and transcriptsFathom OAuth
Circlebackmeetings, transcripts, calendar, email, and action itemsCircleback MCP OAuth
Cal.comscheduling context for reviewed booking actionsCal.com MCP OAuth
Calendlyscheduling context for reviewed booking actionsCalendly MCP OAuth
Google MessagesAndroid Messages web shortcutGoogle Messages web pairing
Pocket AIhardware recordings, summaries, and action itemsPocket AI auth

​
LinkedIn

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.
  • Fathom and Pocket AI can connect before native bulk sync is available.
  • Google Messages opens the web pairing shortcut and is not native message sync yet.
  • LinkedIn uses explicit sync and history import controls to stay conservative.
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.