Freshsales
Find and add Freshsales contacts, and log notes and follow-up tasks during calls.
Your receptionist can recognize callers who are already in Freshsales, add new callers as contacts, note what each caller wanted, and create a follow-up task for your team. There are two ways to connect:
- Webhook tools call Freshsales’ API directly, with no Zapier account and no Zapier task usage. Freshsales’ API looks contacts up by name or email address, not by phone number, so your receptionist finds callers by their email address.
- Zapier can also find callers by phone number, but each action uses tasks from your Zapier plan.
Use webhook tools unless you need to recognize callers by phone number.
Option 1: Webhook tools (recommended)
Get your API key and bundle alias
In Freshsales, select your profile picture, open Profile Settings, and go to the API Settings tab. Copy Your API key and the bundle alias below it, which looks like yourcompany.myfreshworks.com/crm/sales. In the URLs below, replace BUNDLE_ALIAS with it, without https://.
The key acts as your user and can do anything you can in Freshsales. Consider creating it from a user whose role only allows working with contacts, notes, and tasks.
Find the IDs to fix
New contacts and tasks need the ID of the user who owns them, and you can also fix the lead source and lifecycle stage of new contacts. Run these in a terminal, replacing YOUR_API_KEY and BUNDLE_ALIAS, and note the id of each value you want:
Create the webhook tools
For each tool below, go to Integrations, select Add integration, and choose Webhook Tool. Every tool sends the same header: Authorization (Secret), set to Token token= followed by your API key.
Find the caller
Freshsales only returns exact matches, so the receptionist should confirm the spelling of the email address with the caller.
Add the caller
Select Add field on contact for each of these:
first_name(string, required, from the conversation): “The caller’s first name.”last_name(string, from the conversation): “The caller’s last name, if they gave it.”mobile_number(string, required, from the conversation): “The caller’s phone number in international format, for example +14155550123.”emails(array, from the conversation): “Exactly one item, for the caller’s email address. Leave it out if they didn’t give one.” Under Each item, chooseobjectand add two fields:value(string, required, from the conversation): “The caller’s email address.”is_primary(boolean, fixed value):true
owner_id(integer, fixed value): the owner’s IDlead_source_id(integer, fixed value): the lead source’s ID, if you want onelifecycle_stage_id(integer, fixed value): the lifecycle stage’s ID, if you want one
Log a note
Select Add field on note for each of these:
description(string, required, from the conversation): “What the caller wanted, in a few sentences.”targetable_type(string, fixed value):Contacttargetable_id(integer, required, from the conversation): “The contact’s id fromfind_freshsales_contactorcreate_freshsales_contact.”
Create a follow-up task
Select Add field on task for each of these:
title(string, required, from the conversation): “For example: Call back Jane Doe about a quote.”description(string, from the conversation): “The caller’s name, phone number, and what they need.”due_date(string, required, from the conversation): “When the team should call back, as an ISO 8601 date and time, for example 2026-06-21T11:00:00Z.”owner_id(integer, fixed value): the ID of the user who handles callbackstargetable_type(string, fixed value):Contacttargetable_id(integer, required, from the conversation): “The contact’s id fromfind_freshsales_contactorcreate_freshsales_contact.”
The owner and the record types are fixed values, so new contacts and tasks always go to the people you chose, even if the AI sends other values.
find_freshsales_contact returns whatever is saved on the contact. Add a
rule telling your receptionist to never
read a contact’s details back to the caller, and to use them only to recognize the caller.
Select Enable on each tool, then test your receptionist as a new caller who gives their email address and asks for a callback. The contact, a note, and a task appear in Freshsales.
Option 2: Zapier
Add the Freshsales actions
In your Zapier MCP server at mcp.zapier.com, add the actions below from the Freshsales Suite app and connect your Freshsales account. For each field, either set a fixed value or let the AI fill it in, as listed.
Assign the tools
In Reception.ai, open the Zapier integration’s Tools tab, select Refresh tools, and assign each action as listed.
Test it
Test your receptionist as a new caller who asks for a callback. The contact, a note, and a task appear in Freshsales.
Zapier actions
Find the caller
Add the caller
Log a note
Create a follow-up task
Whichever option you use, add a procedure so your receptionist searches for the caller first and only creates a contact when no match is found.
Limitations
- Freshsales doesn’t allow two contacts with the same mobile number or email address, so creating a contact fails for a caller who is already saved. Your receptionist should search first.
- With webhook tools, your receptionist finds callers by email address only. To find them by phone number, use Zapier’s Find Contact by Unique Fields.
- Zapier’s Freshsales app can’t check anyone’s availability, so your receptionist can’t safely book meetings in Freshsales. Use the follow-up task instead, or Reception’s own booking with Google Calendar.
- With Zapier, each action your receptionist runs uses tasks from your Zapier plan. Zapier currently counts two tasks per successful call; failed calls aren’t counted. When the plan runs out, the actions stop until it resets.