Your own Claude and AI key, your data providers on your own keys, replies to your CRM, alerts to Slack and bookings back from your calendar. Anything else can listen to signed webhooks.
Discover suggests what fills the gaps in your setup: a CRM, a chat alert, a scheduler and an address verifier. Connect starts in place, and a connection that needs attention shows up without a refresh.
In HubSpot mode, deals, tasks and notes are HubSpot's own records, written there first. Sends, replies, bounces and meetings land on the contact's timeline, and a deal opened in HubSpot stops the contact's campaigns.
Sync health shows what is waiting, what failed and why, and when each kind of record was last pulled. Each mapped field picks a direction: the most recent edit wins, or one side always does. Pipedrive works the same way, and Salesforce syncs both ways with rules of its own.
Pick an inbox channel and every human reply is posted there, one thread per conversation, with the mailbox, the campaign and the intent. Reply, draft with AI, mark it interested or take it, right from the message.
Reply opens a form with the recipient and subject fixed, and sends from the conversation's mailbox, as you, with the same checks as the dashboard. Notifications can go to their own channels, and the assistant answers when you mention it.
Subscribe any HTTPS address to the events you care about. Each delivery is signed with the endpoint's secret, logged with its response code, and retried with backoff for up to 8 attempts. Private or unsafe addresses are refused.
Build your own with the APIPaste the URL your instance mints into Calendly or Cal.com. Booked, rescheduled and canceled calls appear on the Meetings page and the contact's timeline as they happen, and can start an automation.
Update contacts and log replies, or run your whole CRM on HubSpot.
Two-way sync: activity on the timeline, lead status written back, opt-outs both ways.
Create people on reply, or run your whole CRM on Pipedrive.
Create or update a lead when someone replies.
WhatsApp through a self-hosted WAHA sidecar, LinkedIn through a self-hosted sidecar on your own workers, and an enrichment waterfall across several providers on your own keys are planned. See the roadmap
Once the operator has registered your instance’s own HubSpot, Salesforce, Pipedrive or Slack app, each workspace connects with one sign-in. Close and the verification services take an API key from that service.
Instead of keeping its own deals and pipelines, SalesOS works directly on your CRM’s records: every change is written to your CRM first, and anything your CRM refuses is not saved.
Yes. Point a webhook at it, or use Zapier, Make or n8n. Every event can be sent to any HTTPS address, signed so the receiver can check it came from you.
No. The names here describe what SalesOS connects to. None of these companies is a partner of the project or endorses it.
Tokens and keys are encrypted with your workspace’s own encryption key before they are stored, and you can disconnect any integration at any time.
Integrations are not a data supply. SalesOS sells no contact data; every provider here runs on your own account and key, under that provider's terms.
Install the instance, connect your Claude, your CRM and Slack, and replies flow where your team already works.
