Keep the CRM you already run: Salesforce and HubSpot connect two ways. Send and schedule from your own mailbox and calendar. Approve drafts from Slack or Teams without opening SealDeal.
Everything the app does is also available over a documented REST API with scoped tokens and HMAC-signed webhooks, which is how Zapier and Make are driven.
It does not connect to Dynamics 365, it has no native connector for other CRMs, and it does not sell prospect data.
Direction is from SealDeal's side: in means data arrives, out means it leaves, two-way means both. Setup is where an admin switches it on.
| Integration | What it does | Direction | Plan | Setup |
|---|---|---|---|---|
| CRM | ||||
| Salesforce | Two-way contact sync and activity write-back; with the add-on, account and opportunity import, deal push and AI digest | Two-way | Contact sync on every plan. Import, deal push and digest: $49/mo add-on, Core and above. | Admin, Integrations, Salesforce |
| HubSpot | Two-way contact sync and note write-back; with the add-on, company and deal import, deal push and AI digest | Two-way | Contact sync on every plan. Import, deal push and digest: $49/mo add-on, Core and above. | Admin, Integrations, HubSpot |
| Email and calendar | ||||
| Sends approved drafts, and lands replies back on the deal | Two-way | Every plan. Managed sending is capped at 200 a day per rep. | Admin, Integrations, Email | |
| Calendar | Real availability into the times a draft proposes; booked meetings onto the deal | Two-way | Every plan. | Each rep, on their own Preferences page |
| Chat | ||||
| Slack | Event alerts, approve or reject a draft in place, and a bot that answers pipeline questions | Two-way | Every plan. | Admin, Integrations, Slack |
| Microsoft Teams | Event alerts, approve or reject a draft in place, and the same bot as Slack | Two-way | Every plan. | Admin, Integrations, Teams |
| Telegram | Event alerts into a chat, through a bot you create and hold the token for | Out | Every plan. | Admin, Integrations, Telegram |
| Developer | ||||
| API keys | Scoped bearer tokens for the REST API, per resource and per direction | Two-way | Every plan. | Admin, Integrations, API keys |
| Webhooks | HMAC-signed platform events delivered to your own endpoints | Out | Every plan. | Admin, Integrations, Webhooks |
| Signals | Buying signals POSTed in from your own tooling, as evidence the engine can cite | In | Every plan. | Admin, Integrations, Signals |
| Automation | ||||
| Zapier | Zaps triggered by any platform event, plus actions that write back into SealDeal | Two-way | Every plan. | Admin, Integrations, Automation |
| Make | Make scenarios triggered by the same events, over the generic webhook bus | Out | Every plan. | Admin, Integrations, Automation |
| Event routing | Chooses which platform events each connected channel actually receives | Settings | Every plan. | Admin, Integrations, Event routing |
SealDeal is a full CRM, so you do not need another one. If you already run Salesforce or HubSpot and intend to keep it, the two-way connection lets that system stay your record of truth while SealDeal supplies the grounded next move.
Contact sync and Task write-back are included on every plan. Add the Salesforce sync add-on and SealDeal also imports your Accounts, open Opportunities, contact roles and logged activity, pushes deals back, and writes its AI digest onto the record.
The coexistence import, deal push and digest write-back are a $49/month add-on on Core and above. Imported opportunities stay out of the win-probability model until they have accrued real signal in SealDeal, so you never get a confident score computed from an empty record.
Contact sync and Note write-back are included on every plan. Add the HubSpot sync add-on and SealDeal also imports your Companies and Deals, pushes deals back, and writes its AI digest onto the record.
The coexistence import, deal push and digest write-back are a $49/month add-on on Core and above. Matching is on the HubSpot record id, so re-running an import never duplicates anything.
Outbound goes from your own mailbox under your own domain, so your sending reputation is yours and stays yours. One transport is the exception and it is opt-in: managed sending, for an org with nothing connected yet, goes out from a SealDeal address and is capped low on purpose.
Send under your own domain from your own mailbox. Three transports do that: per-rep Google or Microsoft OAuth mailboxes, or your own SMTP relay. A fourth, managed sending, goes out from a SealDeal address instead and exists so an org with nothing connected yet can still send on day one.
Managed sending is the exception to "your domain, your reputation": it is the platform-operated transport, running on SealDeal's own credentials rather than a key of yours, so those emails leave from a SealDeal address with replies routed back to you. It is capped at 200 a day per rep and is meant as a quick start, not a destination. Every transport except rep mailboxes must also pass a test send before anything leaves; until it does, queued sends are held rather than delivered, because a silent misconfiguration that mails your prospect list from the wrong address is not recoverable.
Each rep connects their own Google or Microsoft 365 calendar, or subscribes a read-only ICS link. Real availability feeds the times a draft proposes, and booked meetings mirror onto the deal.
Reps connect individually from their own Preferences page, so there is no org-wide calendar switch for an admin to flip.
The approval step is where a rep decides what sends, so it should happen where the rep already is. In Slack and Teams that means approving a draft from the notification itself.
Route replies, bookings, bounces and pipeline events to the channels you choose, and approve or reject a draft from the Slack message itself without opening SealDeal. Mention or DM the bot to get your day ranked, ask a grounded pipeline question, draft a reply, add a note, or move a deal to the next stage. Every write asks you to confirm before it runs.
Reply alerts and draft approval in Teams, with the same event routing and the same approve-before-send rule as everywhere else. The same bot answers pipeline questions, drafts replies, adds notes, and moves deals from a Teams chat, with the same confirm-before-write rule.
Platform events land in a Telegram chat through a bot you create and hold the token for, with the same per-channel event routing as Slack and Teams.
Notifications only. Approving or rejecting a draft from the message itself works in Slack and Teams, not in Telegram.
Everything the app does through its own UI is available over a documented REST API with scoped tokens, plus signed webhooks in both directions.
Mint scoped bearer tokens for the public REST API. Scopes are per resource and per direction, so a token that reads contacts cannot write deals or send drafts.
Stream platform events to your own endpoints, HMAC-signed so you can verify each delivery came from SealDeal and was not replayed.
POST buying signals into SealDeal from your own enrichment or intent tooling, Clay, Common Room, or an in-house scraper, over a signed webhook. They become evidence the engine can cite.
If a workflow is not worth writing code for, the event bus drives it. Every platform event can fan out to the tools you already automate with.
Trigger Zaps from any platform event, including the rule-qualified rule.* events your own custom rules emit, and create contacts or deals, tag, pause a sequence or suppress an address from a Zap.
The SealDeal Zapier app carries triggers for platform events plus actions to create contacts and deals, tag, pause a sequence and suppress an address. If you would rather not use it, every one of those is reachable over the raw webhook bus and the public API.
Drive Make scenarios from the same platform events, with no code. Point a Make webhook module at a SealDeal endpoint and every event you subscribed it to arrives signed.
There is no dedicated Make app, and none is in progress. Make is driven through the generic webhook bus, so you build the scenario from a webhook trigger rather than picking SealDeal from their app list.
One place to decide which of the platform events each connected channel actually receives, so Slack does not get everything Teams gets.
Better to know now than in week two of a trial.
Scoped and designed, not built. There is no Dynamics connector today and no date to quote. Dynamics shops can use the public API and webhooks in the meantime.
No native connector. The public API covers contacts, companies, deals, sequences, drafts and events, so a sync is buildable, but you would be building it.
SealDeal does not sell prospect data. It researches the companies and people you bring it from public sources. Signals is the inbound door for data you source elsewhere.
Email only. There is no LinkedIn automation, and none is planned.
Either. SealDeal is a full CRM and can be your system of record. It also has a two-way connection to Salesforce and HubSpot built for coexistence, where that system stays the record of truth and SealDeal supplies the grounded next move, mirroring its activity back. Which mode you run is a setting, not a different product.
Yes, that is what the coexistence import is for. It pulls accounts or companies, open opportunities or deals, contact roles and logged activity, matched on the CRM record id so re-running it never duplicates anything. You can keep the old CRM running the whole time.
No, and you should not want to. Outbound goes from your own mailbox under your own domain, through per-rep Google or Microsoft OAuth, your own SMTP relay, or managed Resend. The sending reputation you build is attached to your domain rather than to a pool shared with every other customer.
Every platform event can drive a Zap or a Make scenario over the webhook bus, and event routing decides which connected channel receives which events. There are 17 platform events covering replies, bookings, bounces, deal stage changes, wins and losses, inbound leads, approvals, list uploads, quota warnings and dead-lettered sends.
Yes. 62 REST endpoints covering contacts, companies, lists, deals, sequences, drafts, action items, suppression, events, analytics and webhooks, with 17 scopes so a token can be narrowed to exactly what it needs. There is an OpenAPI 3.1 schema, and the documentation is public and requires no account to read. Every error it returns is documented too, one page per problem type.
Not today. It was scoped and designed and then deliberately deferred, so there is no connector and no date worth quoting. A Dynamics shop can use the public API and webhooks in the meantime, which is a real amount of work and we would rather say so than imply a connector exists.
Yes, that is what Signals is. POST from Clay, Common Room, or an in-house scraper over a signed webhook, and the signal becomes evidence the engine can cite in a draft rather than an inert field on a record.
Last checked against the running product on 9 September 2026. SealDeal launched that month. This page describes integrations that are built and running; it quotes no customer counts and no case studies, because there are none yet.
Related: What grounded outbound means · How the holdout measures lift · vs HubSpot · vs Salesforce · Security and compliance