Freshsales - Atako

Let your agents manage contacts, accounts, deals, notes and tasks in Freshsales (Freshworks CRM) — search, look up, and keep your pipeline accurate.

Connection

Authentication: API key.
Required settings:
- Subdomain — The subdomain of https://<domain>.myfreshworks.com — e.g. yourcompany for yourcompany.myfreshworks.com

Log in to your Freshsales account → click your profile picture (top right) → Profile Settings → API Settings tab → copy the value in “Your API key”. You also need your Bundle alias (shown below the API key) — it is the subdomain in https://<domain>.myfreshworks.com.See Freshsales’s documentation.

Read actions (13)

Action	Description
`get_account`	Fetch an account (sales account) by id.
`get_contact`	Fetch a contact by id. Optionally embed related data via include: owner, tasks, notes, deals, sales_accounts, etc.
`get_deal`	Fetch a deal by id.
`list_account_views`	List available account views (filters) with their id and name. Pass a view id to list_accounts to fetch accounts from that view.
`list_accounts`	List accounts from a specific view. The view_id comes from list_account_views. Supports pagination and sorting.
`list_contact_views`	List available contact views (filters) with their id and name. Pass a view id to list_contacts to fetch contacts from that view.
`list_contacts`	List contacts from a specific view. The view_id comes from list_contact_views. Supports pagination (page, per_page up to 100) and sorting (sort: lead_score\|created_at\|updated_at\|open_deals_amount\|last_contacted, sort_type: asc\|desc).
`list_deal_stages`	List all deal stages with their id, name and deal_pipeline_id. Use to pick valid deal_stage_id values when creating or updating a deal.
`list_deal_views`	List available deal views (filters) with their id and name. Pass a view id to list_deals to fetch deals from that view.
`list_deals`	List deals from a specific view. The view_id comes from list_deal_views. Supports pagination and sorting.
`list_owners`	List all users (owners) in the Freshsales account — returns id and name for each. Use to resolve owner_id values for contacts, deals and tasks.
`lookup_by_email`	Look up a contact, account or deal by email address. Set f=email and provide the email in q. Use entities to restrict the search (e.g. entities=contact).
`search`	Search across contacts, accounts and deals by keyword. Use the include param to narrow results to specific entity types (e.g. include=contact,sales_account,deal).

Write actions (7)

Action	Description
`add_note`	Add a note to a contact, account or deal. Body: { “note”: { “description”: string (XHTML body), “targetable_type”: “Contact”\|“SalesAccount”\|“Deal”, “targetable_id”: integer } }. targetable_id is the id of the contact, account or deal.
`create_account`	Create an account. Body: { “sales_account”: { “name”: string, “website”: string, “phone”: string, “industry_type_id”: integer } }.
`create_contact`	Create a contact. Body: { “contact”: { “first_name”: string, “last_name”: string, “email”: string (deprecated, use “emails”), “mobile_number”: string, “job_title”: string, “owner_id”: integer, “sales_accounts”: [{ “id”: integer, “is_primary”: boolean }] } }. At least email or mobile_number is required.
`create_deal`	Create a deal. Body: { “deal”: { “name”: string, “amount”: number, “sales_account_id”: integer, “deal_stage_id”: integer, “expected_close”: string (YYYY-MM-DD), “owner_id”: integer } }. deal_stage_id comes from list_deal_stages.
`create_task`	Create a task. Body: { “task”: { “title”: string, “description”: string, “due_date”: string (YYYY-MM-DDTHH:MM:SSZ), “owner_id”: integer, “targetable_type”: “Contact”\|“SalesAccount”\|“Deal”, “targetable_id”: integer } }. owner_id comes from list_owners.
`update_contact`	Update a contact by id. Body: { “contact”: { …fields to update } }. Same fields as create_contact.
`update_deal`	Update a deal by id. Body: { “deal”: { …fields to update } }. Same fields as create_deal.

Permissions

Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.

Last reviewed against the provider API: September 2026.