SocialOSExplore the demo
Planned integrations

Your tools.
The context you choose.

Explore proposed connections for email, meeting notes, contacts, documents and AI assistance. Each starts with what you select and explains what could appear in the relationship workspace.

Try the note-review workflow

All connections below are planned. The examples use fictional data. Mapping a sample or previewing a digest does not connect an account, import a file or send an email.

13 planned connections

WhatsApp Business

Planned

A place to send the note before it slips your mind.

See the proposed workflow
You choose
Send one note to your linked SocialOS capture chat.
What appears
Review a suggested person, conversation note and next action.

Fictional example

“Met Maya after the panel. Offer an introduction next week.” becomes a note and separate suggestions for you to review.

This proposed connection is for a linked business capture chat. It does not provide unrestricted access to personal WhatsApp history.

Meta Cloud API documentation (opens in a new tab)

Gmail

Planned

Keep the email that explains the relationship.

See the proposed workflow
You choose
Choose the conversations you want to include. Configure your email digest separately.
What appears
A dated conversation in the person’s history, with a separate preview of the digest you choose to receive.

Fictional example

Select Maya’s meeting thread for her timeline. Choose a weekly digest of your upcoming follow-ups independently.

A separate email digest

Digest is off in this sample. Selecting a conversation does not turn it on.

Reading selected context and sending through an email account are separate capabilities. Provider permissions and delivery setup would be required for the planned connection.

Gmail permissions documentation (opens in a new tab)

Granola

Planned

Carry the useful parts of a meeting forward.

See the proposed workflow
You choose
Choose accessible meeting notes, then review the people and firm matches.
What appears
A source-dated meeting entry with separately reviewable updates and tasks.

Fictional example

Alex owns the relationship. Maya is an attendee. A selected meeting note supports the proposed interest update.

Access depends on your Granola plan and permissions. A note owner, meeting organiser, speaker and relationship owner are different roles.

Granola API documentation (opens in a new tab)

Fireflies

Planned

Give a meeting transcript the right context.

See the proposed workflow
You choose
Select a meeting transcript and confirm who it belongs with.
What appears
A useful conversation entry, with supporting excerpts beside suggested next steps.

Fictional example

Inspect Maya’s words, confirm the contact match and choose whether to keep the proposed introduction task.

A transcript speaker is not automatically the relationship owner. Meeting access follows the provider’s permissions and plan.

Fireflies transcript documentation (opens in a new tab)

CSV import

Planned

Give the spreadsheet a considered new home.

See the proposed workflow
You choose
Map incoming columns to people, firms and notes. Review possible duplicates.
What appears
An import preview that shows what would be created, matched or held for review.

Fictional example

Map “Full name” to Person, “Company” to Firm and “Meeting notes” to Note. Flag Maya Chen as a possible existing contact.

Preview sample mapping

Three columns. One possible duplicate. No file upload.

This website uses a sample mapping. No file is uploaded or imported.

Firecrawl

Planned

Fresh context, with the source still attached.

See the proposed workflow
You choose
Choose a public website page to check, then inspect each proposed update.
What appears
A source-dated website suggestion that can be compared with the person’s conversation history.

Fictional example

An older website says healthcare. A newer conversation says industrial software. Keep the current value you choose and retain both sources.

A website check date is not a guarantee that its contents are current. Public claims do not automatically override your direct conversations.

Firecrawl scrape documentation (opens in a new tab)

EmailBison

Planned

Keep useful replies in the relationship story.

See the proposed workflow
You choose
Choose lead and reply context from one EmailBison workspace, then confirm the person match.
What appears
A dated reply in the right person’s history, ready for partnership follow-through.

Fictional example

A reply about a commercial partnership becomes context for Daniel’s record, with the original workspace identified.

The proposed connection is workspace-scoped. This preview does not send outreach or claim access across all workspaces.

EmailBison authentication documentation (opens in a new tab)

Google Drive

Planned

Keep the client brief within reach of the relationship.

See the proposed workflow
You choose
Choose the files that support a mandate, then confirm the people and firms they belong with.
What appears
A document reference and selected context beside the relationship, ready for your review.

Fictional example

Select Northline’s client brief. Keep its expansion plans and founder-control preference beside the mandate, with a link back to the file.

The planned connection would require Google authorization and file permissions. It would not make a private document public or automatically ingest the whole drive.

Google Drive file-access documentation (opens in a new tab)

Outlook

Planned

Bring the investor’s reply back to the mandate.

See the proposed workflow
You choose
Choose an email thread and review the relationship match before keeping its context.
What appears
A dated conversation and separately reviewable follow-up, with the original message identified.

Fictional example

An investor asks for a revenue-retention breakdown. Keep the question with Northline and review a follow-up for the relationship owner.

Thread selection is a proposed SocialOS control. Microsoft mailbox permissions and firm approval would still be required. Sending mail is a separate capability.

Microsoft Graph mail documentation (opens in a new tab)

OneDrive

Planned

Keep supporting documents beside the decision.

See the proposed workflow
You choose
Choose an accessible document, then review which mandate and relationship it supports.
What appears
A reference to the original file and selected details that can inform the next client discussion.

Fictional example

Link the CFO’s cohort breakdown to the outstanding investor question, preserving the file reference for the next discussion.

Access would depend on Microsoft authorization, the file’s permissions and the firm’s configuration. The proposed connection does not grant access to every file or change its sharing settings.

Microsoft Graph file documentation (opens in a new tab)

DocuSign

Planned

Keep agreement progress in the mandate’s context.

See the proposed workflow
You choose
Choose the relevant agreement envelope and confirm the mandate it belongs with.
What appears
A dated agreement-status entry and a suggested follow-up for you to review.

Fictional example

Record that Northline’s engagement-letter envelope is complete, then review the next preparation step with its owner.

An envelope’s status is not confirmation that a transaction has closed. Account permissions and event setup would be required; this website does not send or sign documents.

DocuSign envelope documentation (opens in a new tab)

Claude

Planned

Prepare a considered brief from the context you select.

See the proposed workflow
You choose
Choose the notes and documents an authorized Claude model may use for a specific question.
What appears
A draft briefing that separates supported details from questions still open, for your review.

Fictional example

Ask for a meeting brief from the client objective and latest investor note. Review every statement and keep cheque range marked as unconfirmed.

Planned assistance would use the Claude API, subject to firm setup and provider terms. Selected context would be sent to the configured provider. It does not import private Claude chat history or make decisions for you.

Claude Messages API documentation (opens in a new tab)

ChatGPT

Planned

Turn selected context into a draft you can work with.

See the proposed workflow
You choose
Choose the relationship context and the briefing or draft you want help preparing.
What appears
A proposed discussion outline or introduction draft, ready to inspect and refine before use.

Fictional example

Prepare an introduction draft from the confirmed people and shared context. Review the wording, permissions and recipient before using it.

Planned assistance would use OpenAI’s API, subject to firm setup and provider terms. Selected context would be sent to the configured provider. It does not import private ChatGPT chats, send messages or act on your behalf.

OpenAI text-generation documentation (opens in a new tab)

Gmail and Google Drive are trademarks of Google LLC. Outlook and OneDrive are Microsoft trademarks. ChatGPT is a trademark of OpenAI. Other product names and logos belong to their respective owners. Their appearance identifies a proposed connection and does not imply a partnership or endorsement.

One review principle

Bring in the source.
Keep the decision.

A selected conversation can add a useful detail. An older website can raise a question. Keep both tied to their origin, then decide what should become part of the record.

Proposed AI assistance would use an authorized provider connection and its configured scope. It is not a promise to import private Claude or ChatGPT conversations.

Read about privacy and control
See it for yourself

Your next move,
in context.

Open a relationship. Review a conversation. Find a route into your next mandate.

Enter the workspaceInteractive sample. Fictional data. No signup.