SealDeal connects to Salesforce and HubSpot two ways, sends from your own Google, Microsoft or SMTP mailbox, syncs each rep's calendar, posts to Slack, Microsoft Teams and Telegram, and exposes everything it does over a documented REST API with scoped tokens and HMAC-signed webhooks, which is also 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.
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 work on any paid 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 work on any paid 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 out under your domain from your mailbox, never from a shared vendor pool, so your sending reputation is yours and stays yours.
Send from your own mailbox and your own domain. Three transports: per-rep Google or Microsoft OAuth mailboxes, your own SMTP relay, or managed Resend.
An org using SMTP or managed Resend must pass a test send before anything leaves. Until it does, queued sends are held rather than delivered, which is deliberate: 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.
Reply alerts and draft approval in Teams, with the same event routing and the same approve-before-send rule as everywhere else.
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 dedicated Zapier app is still going through Zapier review and is not listed in their public directory yet. Everything above works today over webhooks and the public API regardless.
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.
Make is driven through the generic webhook bus rather than a dedicated Make app, so you build the scenario from a webhook trigger instead of 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.
Worth knowing before a trial rather than during one.
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 11 platform events covering replies, bookings, bounces, deal stage changes, wins and losses, inbound leads, approvals, list uploads, quota warnings and dead-lettered sends.
Yes. 45 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.
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.
SealDeal is pre-launch. 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