Freshsales integration

Video engagement as notes on the Freshsales contact

Launch a video campaign in Zidi and each recipient is matched to a Freshsales contact by email address, or created as one. Opening the video writes a note; finishing it or pressing the call-to-action writes a second note carrying the percentage watched.

Nothing custom is added to your account. No modules, no fields, no tags — just notes on the contacts your team already works, which is why it takes about a minute to set up and nothing to maintain.

Open Zidi and connect New to Zidi? Start free

How to connect Freshsales

1
Find your bundle alias
It is the first part of the address you use to reach Freshsales. If your team signs in at acme.myfreshworks.com then your alias is acme. Zidi asks for the alias rather than the whole address so it can build the API host itself.
2
Generate an API key
In Freshsales, open your profile settings and copy the API key shown there. The key inherits the permissions of the user it belongs to, so use an account that can see and edit the contacts you plan to sync.
3
Paste both into Zidi
Open Integrations in Zidi, choose Freshsales, and enter the alias and the key. Zidi checks them against your account before saving, so an incorrect pair is refused on the spot rather than failing at the first campaign.

Freshsales syncing is on the Zidi Pro plan, verified on the server rather than only in the interface. The alias must be the short name from your Freshworks address, between two and sixty-three characters of letters, numbers and hyphens; pasting the full https address is the single most common mistake and Zidi will reject it rather than guess at what you meant.

What syncs, and when

What happens in Zidi	What appears in Freshsales
Campaign launched	Zidi searches your contacts for the recipient's email address, creates one when there is no match, and writes a note holding their personalized video link and the campaign it belongs to.
Recipient opens their video page	A note is added to the contact. It opens with the line “Zidi Video Engagement” and your campaign name, and says they opened the page and when.
Recipient finishes the video or clicks the call-to-action	A second note, starting with that same line, gives the highest percentage reached, the milestones passed and whether the button was pressed.
Someone you know opens a directly shared video	A single note appears when they pass the halfway mark and is rewritten as they reach eighty per cent and the end, so one viewing produces one note rather than three. The contact has to be in Freshsales already, because this path writes notes without creating anybody.

A Freshsales note is a description with no separate subject, so both notes begin with the words “Zidi Video Engagement” and differ in what follows. Everything moves in one direction. Zidi searches for a contact by email to decide where a note belongs, and never reads, imports or exports your Freshsales data. Campaign engagement is queued and held for roughly a minute per recipient, so a viewer who jumps around inside a video leaves one clean entry. On the shared-link path the hold does not apply; each view and milestone is deduplicated on its own. Only identified viewers reach Freshsales; anonymous views are counted in Zidi analytics and go no further.

The alias, and why the setup asks for it

Freshworks gives every account its own hostname. Your data lives at a domain built from a short alias, and the API answers on that same domain, so Zidi cannot call anything until it knows which one is yours. Asking for the alias rather than the full address keeps the field unambiguous: there is exactly one right answer, it is visible in your browser whenever you are signed in, and there is no protocol or trailing slash to get wrong. Zidi validates the shape before it saves, so a value with a dot in it or a pasted https address is refused immediately rather than being stored and failing silently the first time you launch a campaign.

The API key is ordinary Freshsales credentials. It carries the permissions of whoever generated it, which means the cleanest arrangement is a user who can already see the contacts your campaigns will touch. Zidi stores it encrypted and it never leaves the server.

What your account looks like afterwards

Exactly as it did before, plus notes. This is among the plainest of the CRM connections Zidi offers, alongside Copper, and deliberately so. It creates no custom fields waiting to be filled, adds no tags to maintain and defines no new record types, so there is nothing for an administrator to review and nothing that needs undoing if you stop using it. A rep opens a contact, reads the activity, and sees the video alongside the emails and calls in the order things happened.

That simplicity is also the limit worth knowing. Because engagement arrives as text in a note rather than as a number in a field, Freshsales workflows cannot branch on the watch percentage directly. If you want automated branching on how much of a video someone watched, ActiveCampaign's tags are the sharper tool. For teams that mainly want the rep to know before they call, notes are the whole job and they arrive without any configuration at all.

Freshsales integration questions

Where do I find the bundle alias?

In the address bar. Sign in to Freshsales and look at the hostname: the part before myfreshworks.com is your alias. Enter that short name on its own, without the protocol and without the rest of the domain, and Zidi assembles the API address from it.

Does Zidi add custom fields to my account?

No. Freshsales is one of the connections where Zidi creates nothing beyond notes on contacts — Copper is the other. There are no custom fields, no tags and no new modules, so there is nothing for an administrator to approve beforehand and nothing left behind if you disconnect.

How many notes will one recipient produce?

Two at most from a campaign: one when they first open the page and one when they finish or press the button. The intermediate milestones are listed inside that second note rather than each triggering a write, which is what keeps a busy contact readable. A directly shared video adds a single note that is rewritten as the viewer gets further.

What happens if the API key stops working?

The writes fail and are retried, and the connection stays visible in Zidi so you can paste a fresh key without setting anything else up again. Because keys inherit their owner's permissions, the usual cause is the underlying user losing access to a group of contacts rather than the key itself expiring.

Which Zidi plan is required?

Pro. The check runs on the server when you save the credentials and again before every write, so a workspace that drops off Pro pauses syncing while keeping the connection. Upgrading again resumes it without another setup step.

Still stuck? Email support@zidi.ai or contact our team.

Other Zidi integrations

Copper

Paste a Copper API key and the login email that made it. Recipients become People and engagement is logged as Activities on the contact.

HubSpot

Campaign recipients become HubSpot contacts matched by email, and video engagement lands on the contact as five custom properties Zidi creates plus a note.

Salesforce

Recipients are matched or created as Contacts; opens, completions and CTA clicks are logged as completed Tasks on the activity timeline.

Zoho

Connect any of Zoho CRM's data-centre regions with OAuth. Recipients sync as Contacts and engagement is written as Notes on the contact.

ActiveCampaign

Connect with your API URL and key. Recipients sync as Contacts with Notes, and Zidi applies engagement tags such as Watched Video and High Engagement.

Connect Close with OAuth. Recipients are matched by email and video engagement is written as note Activities on the record.

Monday.com

Pick a board, paste an API key, and each recipient becomes a board item whose updates record how far they watched and whether they clicked.

Zapier

Zidi is a public app in the Zapier App Directory, with five triggers: video viewed, video uploaded, CTA clicked, campaign launched and watch threshold.