Dialer + CRM stack

Klenty + HubSpot: dialer calls tied to meetings and deals

Count Klenty dialer calls and conversations per rep and per cadence beside HubSpot meetings and pipeline, and keep call history beyond Klenty's 30-day API window.

Start 7-day free trial Talk to us

7-day free trial • No credit card required • 5-min setup

The question this page answers

Which Klenty cadences and callers lead to HubSpot meetings and deals?

Why Klenty and HubSpot do not line up on their own

Klenty knows the caller, the cadence the call belonged to, the prospect and whether the call became a conversation. It has no record of the deal that followed, and its API returns only the last 30 days of calls.

HubSpot knows the deal, its amount, stage and create date, the contacts and company associated with it, its owner, and the meetings and calls logged against those contacts. It does not show, on its own, how many dials and conversations each rep made to get there.

Depending on how your native sync is set up, Klenty calls may also be logged on HubSpot contact records. Whether those logs carry an outcome you trust, and whether they add up to dials, conversations, meetings and pipeline per rep, depends on that setup.

Klenty's API is per user: a key reads one login's data unless teammates are listed, and call history goes back 30 days. A team-wide, quarter-long view of calls against pipeline is not something a single Klenty export hands over.

How OutboundManager joins Klenty and HubSpot

Klenty dialer seats (the key's user, the teammates you list and the callers seen on calls) are each mapped to a rep. HubSpot owners are mapped to reps the same way, so one rep row holds their Klenty seat and their HubSpot owner.
Outbound Klenty calls sync with their outcome. A call counts as connected when Klenty flags the call as connected or as a conversation. Inbound calls are skipped.
When Klenty has an email address for the prospect, the call is attached to the contact with that key: the same contact HubSpot associates with its deals. Contacts are de-duplicated on email address, then LinkedIn URL.
HubSpot meetings count for the rep mapped to the meeting's owner. Deals sync with amount, stage, create date and their associated contacts and companies.
Each deal is credited to the most recent email sent, LinkedIn invite, LinkedIn message or call to any of the deal's contacts, before the deal was created and no more than 120 days before it. When that touch is a Klenty call, the deal goes to the rep who called and to the cadence the call belonged to.
With write-back on, the source campaign, channel, rep and touch date are written to four OutboundManager properties on the HubSpot deal.

A worked example

You connect Klenty with an admin key and list two teammates. The first sync brings in about 30 days of calls for the three logins, grouped by cadence. Six weeks later the scorecard still holds those first calls plus everything synced since, although Klenty's API no longer returns the oldest ones. A deal created in HubSpot after a call to a prospect with a known email address is credited to the caller and the cadence.

What you can see once both are connected

Klenty cadences listed as campaigns, with the deals and pipeline credited to their calls
Call history that keeps growing in OutboundManager after Klenty's own 30-day window has moved on
Calls and connected calls per rep beside meetings and pipeline, each against a weekly target
Deals whose last touch was a call shown with call as the source channel, credited to the rep who dialled
A weekly report that includes calls, connected calls, meetings and new pipeline

Rep scorecard: four reps with sends, LinkedIn touches, replies, meetings, pipeline and won revenue, each shown against a weekly target

The rep scorecard: one row per rep across every connected tool. With a dialer connected, each rep also gets calls and connected calls. Demo data.

Set it up

Connect Klenty

In Klenty, go to Settings → Integrations → Klenty API Key and copy the key. The key belongs to the user who is logged in.
In OutboundManager, an admin opens Settings → Connections and clicks Add connection.
Pick Klenty. Enter the Klenty account email (the login the key belongs to). With an admin key, list teammates' Klenty logins in "Teammates to include", comma separated.
Paste the API key. It is checked against the tool automatically; click Save once it shows Key works. The key is stored encrypted.
Open Settings → Reps & senders and give each dialer seat a rep, so calls land on the right row of the scorecard.

Klenty integration: what syncs and its limits Klenty documentation (opens in a new tab)

Connect HubSpot

In HubSpot, a super admin creates a private app (Settings → Integrations → Private Apps; newer accounts list private apps under Development → Legacy apps).
Give it these scopes: crm.objects.deals.read, crm.objects.contacts.read, crm.objects.companies.read, crm.objects.owners.read and crm.schemas.deals.read. For write-back, also crm.objects.deals.write and crm.schemas.deals.write.
Copy the private app's access token.
In OutboundManager, an admin opens Settings → Connections and clicks Add connection.
Pick HubSpot. Paste the access token. It is checked against the tool automatically; click Save once it shows Key works. The key is stored encrypted.
Map HubSpot owners to reps in Settings → Reps & senders. To write attribution back to deals, turn on write-back on the HubSpot connection; it is off until you do.

HubSpot integration: what syncs and its limits HubSpot documentation (opens in a new tab)

After both are connected

Map senders to reps. In Settings → Reps & senders, give every mailbox, LinkedIn account, dialer seat and HubSpot owner a rep. Re-mapping later moves the history with the sender.
Set weekly targets per rep on the same page, so the scorecard shows each number against a target and the overview flags reps under 60% of it.
Optional: turn on write-back on the HubSpot connection. It is off by default and needs the two deal write scopes; it then fills four OutboundManager properties on each attributed deal.

Good to know

Klenty + HubSpotOutbound calls logged in HubSpot are counted as calls too. If Klenty also logs each call to HubSpot, the HubSpot copy is matched to the Klenty call (same person, within two minutes) and counted once.
Klenty + HubSpotCalls are counted in their own columns. They are not added to the sends that reply rates are divided by.
KlentyKlenty's API only returns calls from the last 30 days, so the first backfill covers about 30 days, not 90.
KlentyKlenty email sends, replies and bounces are only available as totals, so no email activity is imported from Klenty.
KlentyThere is no users endpoint: seats come from the key's user, the teammates you list and the callers on each call.
KlentyKlenty's date filter is unreliable, so every sync reads the widest window and filters records itself.
HubSpotDeal stage history is not synced, only the current stage.
HubSpotInbound calls are skipped, and cancelled meetings are removed.
HubSpotHubSpot search returns at most 10,000 results per query; long deal backfills are read in slices, which takes a little longer.
HubSpotWrite-back only touches deals with an outbound attribution, in a property group named OutboundManager.

Klenty + HubSpot questions

Klenty only returns 30 days of calls. What happens to older ones?

The first sync covers about 30 days. Calls that have been synced stay in OutboundManager, so from then on your history grows past Klenty's window one sync at a time.

Are Klenty email steps part of the picture?

No. Klenty exposes email only as totals, not as individual sends and replies, so nothing would match a person or a deal. This pair is about Klenty calls. Connect your email sender directly for email.

Do I have to switch off my existing Klenty to HubSpot sync?

No. OutboundManager reads from Klenty and from HubSpot separately, each with its own API key, and does the join itself. It does not depend on, replace or interfere with any sync you already run between them.

Can OutboundManager change anything in Klenty or HubSpot?

It only reads from Klenty. In HubSpot it writes nothing unless you turn write-back on; then it fills four deal properties in a group named OutboundManager.

The two tools on this page

See all stacks · See all integrations

See Klenty and HubSpot in one set of numbers.