Skip to navigation

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.

1

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.

2

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:

curl -H "Authorization: Token token=YOUR_API_KEY" https://BUNDLE_ALIAS/api/selector/owners
curl -H "Authorization: Token token=YOUR_API_KEY" https://BUNDLE_ALIAS/api/selector/lead_sources
curl -H "Authorization: Token token=YOUR_API_KEY" https://BUNDLE_ALIAS/api/selector/lifecycle_stages
3

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

FieldValue
Namefind_freshsales_contact
Description”Find the caller in our CRM by their email address. Use it before adding a new contact. Pass the contact’s id to the note and task tools.”
MethodGET
URLhttps://BUNDLE_ALIAS/api/lookup
Request HeadersAuthorization (Secret): Token token= followed by your API key
Query Parametersq (string, required): “The caller’s email address, exactly as they spell it.”
f (string, fixed value): email
entities (string, fixed value): contact
Assign to agentsReceptionist

Freshsales only returns exact matches, so the receptionist should confirm the spelling of the email address with the caller.

Add the caller

FieldValue
Namecreate_freshsales_contact
Description”Add the caller as a contact, only when find_freshsales_contact didn’t find them.”
MethodPOST
URLhttps://BUNDLE_ALIAS/api/contacts
Request HeadersAuthorization (Secret): Token token= followed by your API key
Body Parameterscontact (object, required), with the fields below
Assign to agentsReceptionist

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, choose object and 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 ID
  • lead_source_id (integer, fixed value): the lead source’s ID, if you want one
  • lifecycle_stage_id (integer, fixed value): the lifecycle stage’s ID, if you want one

Log a note

FieldValue
Nameadd_freshsales_note
Description”Note what the caller wanted on their contact, before the call ends.”
MethodPOST
URLhttps://BUNDLE_ALIAS/api/notes
Request HeadersAuthorization (Secret): Token token= followed by your API key
Body Parametersnote (object, required), with the fields below
Assign to agentsReceptionist

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): Contact
  • targetable_id (integer, required, from the conversation): “The contact’s id from find_freshsales_contact or create_freshsales_contact.”

Create a follow-up task

FieldValue
Namecreate_freshsales_task
Description”Create a follow-up task for the team whenever you promise the caller a callback.”
MethodPOST
URLhttps://BUNDLE_ALIAS/api/tasks
Request HeadersAuthorization (Secret): Token token= followed by your API key
Body Parameterstask (object, required), with the fields below
Assign to agentsReceptionist

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 callbacks
  • targetable_type (string, fixed value): Contact
  • targetable_id (integer, required, from the conversation): “The contact’s id from find_freshsales_contact or create_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

1

Connect Zapier

If you haven’t yet, connect Zapier in Reception.ai.

2

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.

3

Assign the tools

In Reception.ai, open the Zapier integration’s Tools tab, select Refresh tools, and assign each action as listed.

4

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

FieldValue
Zapier actionFind Contact by Unique Fields
Set in ZapierThe field to search by: the phone number.
Let the AI fill inThe value to search for: the caller’s phone number.
Assign toClient

Add the caller

FieldValue
Zapier actionCreate Contact
Set in ZapierThe sales owner, the lead source, the lifecycle stage, and any tags.
Let the AI fill inFirst name, last name, mobile number, and email address.
Assign toClient

Log a note

FieldValue
Zapier actionAdd Note
Set in ZapierThe module: Contact.
Let the AI fill inThe contact ID (from the previous actions) and the note text.
Assign toClient

Create a follow-up task

FieldValue
Zapier actionCreate Task
Set in ZapierThe module (Contact) and the owner who handles callbacks.
Let the AI fill inThe title, due date, description, and contact ID.
Assign toClient

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.

Troubleshooting

ProblemWhat to check
401 from FreshsalesThe Authorization header must be Token token= followed by your API key, with no Bearer.
404 from FreshsalesCheck that each URL starts with https://, then your bundle alias, then /api/.
A Freshsales action doesn’t appear in Reception.aiSelect Refresh tools on the Zapier integration after adding actions in Zapier.
An action shows Changed and isn’t usedYou edited it in Zapier. Select Update in the Tools tab.
Known callers aren’t foundWith webhook tools, the email address must match exactly. With Zapier, Freshsales matches phone numbers as stored, so store numbers in one format, or also search by email.
Creating a contact failsThe caller may already be saved with that mobile number or email. Search for them first.
Creating a task failsdue_date must be a date and time Freshsales accepts. If an ISO 8601 value such as 2026-06-21T11:00:00Z is rejected, describe the format from Freshsales’ example instead, such as Tue Jun 21 2026 11:00:00 GMT+0000.
Notes or tasks aren’t linked to the callerYour receptionist needs the contact ID from the find or create tool, or from Find Contact by Unique Fields or Create Contact in Zapier.