Every Norbelys integration, and what it actually does

Five tools connect to Norbelys today, each wired in about a minute, and every one of them is included on every plan — not a tier, not an add-on. This is a plain tour of what each integration actually does, not a marketing list of logos. Full detail lives on the integrations page; this is the version that explains the “why.”

Where you send from, first

Before the integrations, the mailbox layer: Google Workspace and Microsoft 365 connect with one-click OAuth and no stored passwords, any other provider connects over SMTP with replies read over IMAP, and if you’d rather not manage mailbox infrastructure at all, managed sending runs it for you. Unlimited mailboxes on every plan, and every one gets warmup, verification and honest analytics automatically — none of that is gated behind a particular tool integration.

Slack — real replies land where your team already watches

Slack is the simplest of the five and often the most-used: real replies and reputation alerts post directly to the channel your team already has open, instead of living in a dashboard someone has to remember to check. A reply gets classified as human before it ever reaches Slack, so the channel stays signal, not every automated bounce notification mixed in with a genuine prospect response.

HubSpot — contacts in, replies logged, deals attributed back

HubSpot is one of three live CRM integrations, and all three share the same contract: contacts flow in from HubSpot as campaign leads, every human reply logs on the contact’s timeline in HubSpot, and closed deals attribute back to the campaign that started the conversation. Matching happens by email — contacts get updated in place, never duplicated, so running the sync repeatedly doesn’t create a mess to clean up later.

Pipedrive — the same three directions, in Pipedrive’s own objects

Pipedrive gets the identical contract as HubSpot — import, log, attribute — built around Pipedrive’s own object model rather than a generic wrapper. If your team already lives in Pipedrive’s pipeline view, replies and deal attribution show up there without anyone having to check a second system for outbound context.

Salesforce — enterprise CRM, same contract

Salesforce is the enterprise case of the same pattern: matched by email, updated in place, never duplicated. If your org already runs Salesforce as system of record, Norbelys plugs into it the same way it plugs into HubSpot or Pipedrive — the difference is Salesforce’s own object complexity, not a different feature set on Norbelys’s side.

Calendly — a booked meeting stops the sequence, instantly

Calendly closes a loop that’s easy to get wrong manually: the moment someone books a meeting, Calendly tells Norbelys, that counts as a conversion, and the sequence stops. Nobody gets a follow-up email after they’ve already booked time — a small thing operationally, but it’s exactly the kind of detail that erodes trust with a prospect when it’s missed.

Setting up your first integration

Connecting any of the five follows the same shape, whether it’s Slack or a CRM:

Open the integration from your workspace settings and authenticate with the target tool — Slack and the CRMs use OAuth, so there’s no API key to copy and paste by hand.
For a CRM, confirm the matching field. Norbelys matches contacts by email address across HubSpot, Pipedrive and Salesforce, so the sync assumes email is a reliable identifier in your CRM — worth a quick check if your CRM has historically allowed duplicate or missing email fields.
Pick which direction matters most to start. You can bring contacts in as leads immediately, or turn on reply-logging and deal attribution first if you’re mid-campaign and don’t want to disturb an existing contact list yet — the three directions (import, log, attribute) don’t have to switch on all at once.
For Slack, choose the channel, not the workspace — reputation alerts and real replies both post to whichever channel you designate, so picking the channel your outbound team actually watches matters more than granting broad workspace access.
Test with a small batch before trusting it at volume. Send a handful of test replies through and confirm they land correctly classified and attributed before relying on the sync for a live campaign.

None of this requires a developer, but none of it requires not having one either — every step above is also available as a direct API call if you’d rather script the setup than click through it.

Why “included in every plan” is a real claim, not a marketing line

It’s worth being specific about what “included” means here, because a lot of platforms use the word loosely. There’s no integration marketplace with per-connector pricing, no cap on how many CRM records sync per month tied to plan tier, and no “Slack alerts on Scale only” gate hiding in the fine print. Starter, Growth and Scale all get the identical integration surface — the plan differences are about contacts, sends and campaign count, not which tools you’re allowed to connect. That matters most for a small team on Starter deciding whether to wire in a CRM on day one: there’s no reason to wait for a bigger plan to get the full integration set.

For builders: the same API the dashboard runs on

Every integration above is a specific, pre-built wiring of a more general fact: the dashboard runs on the same REST API you can call directly, and Norbelys speaks MCP in both directions — plug Norbe into your own tools, or plug your own agents into Norbelys. If none of the five live integrations covers what you actually need to connect, the API is the sixth option, not a fallback. See why developers pick the Norbelys API for what that surface actually looks like.

Coming from another tool?

If you’re migrating from Apollo, Smartlead, Instantly or Lemlist, Norbelys imports campaigns, contacts and suppression lists directly from those platforms — free, with a human helping through the process rather than a self-serve importer you’re left to figure out alone. See the dedicated guides for switching from Apollo or switching from Lemlist if either is your current setup.

Questions people ask about the integrations

Frequently asked questions

Do any of the integrations cost extra?

No. Like warmup, verification and DMARC monitoring, every integration and every mailbox connection is part of every plan — not a tier, not an add-on. There's no integration marketplace with per-connector pricing to budget around.

What do the CRM integrations (HubSpot, Pipedrive, Salesforce) actually do?

Three things, in both directions: import CRM contacts as campaign leads, log every real human reply on the contact's timeline (matched by email, updated in place, never duplicated), and attribute closed deals back to the campaign that started the conversation.

Are webhooks available yet?

Not yet — event webhooks are explicitly labeled 'on the way' on the integrations page, not live. Until that ships, the REST API and the live CRM integrations are the reliable paths for getting Norbelys event data into your own systems.

Which mailboxes can I actually send from?

Google Workspace and Microsoft 365 connect with one-click OAuth, any other provider connects over SMTP with replies read over IMAP, and managed sending is available if you'd rather not manage mailbox infrastructure at all. Unlimited mailboxes are included on every plan.

Can I use the API alongside the pre-built integrations?

Yes — the pre-built integrations are specific wirings of the same REST API the dashboard runs on. If you need something the five live integrations don't cover, calling the API directly (or building on MCP) is a normal, supported path, not a workaround.

Two clicks connects Gmail or Outlook; each of the five tools above takes about a minute to wire in. Start with the integrations page for the live constellation, or pricing if you’re ready to see where these fit into a plan.