Freshsales
Freshsales contact and deal events into your workflow
Freshsales is the Freshworks-family CRM that often comes packaged with Freshdesk for teams that want one vendor across sales and support. Four triggers cover the events you'd actually want to act on: Contact Created, Contact Updated (any field change), Deal Created, Deal Updated. Twelve actions cover writes and reads: Create Account, Create Contact, Create Deal, Delete Contact, Delete Deal, Get Contact, Get Deal, List Contacts, plus the related entity actions. The integration uses a Freshsales API key from your account profile. The connection respects Freshsales's territory and role-based access, workflows only touch records the connected user has visibility into. Common patterns: a Freshsales Deal Created with deal stage equals "Qualified" syncs the contact into Freshdesk as a high-priority support contact (with the deal value visible to the support team), or a Contact Updated with the lead score field crossing a threshold triggers a Slack alert to the assigned AE.
Workflows start when Freshsales does.
4 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new contact is added to the Freshsales CRM. The base hook for "new lead → enrichment + Slack ping + onboarding sequence" cross-app workflows.
Fires on any contact change. For specific transitions (lifecycle stage change, owner reassignment), filter the payload before downstream side-effects.
Fires on new deal creation. Payload includes value, stage, owner, contact. The pipeline-growth hook for revenue forecast updates and AE notifications.
Fires on any deal change. For "stage moved to Closed Won" automation specifically, filter the payload's stage field.
Do anything Freshsales can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Freshsales Account | Creates a company/account record. Useful for "new B2B prospect → account record before contact" workflow patterns. |
| Create Freshsales Contact | Creates a new contact with email (dedupe), name, custom fields, and optional account association. The base hook for "form submission → push to Freshsales" sync workflows. |
| Create Freshsales Deal | Creates a deal with name, amount, pipeline, stage, contact. For "qualified lead → auto-create deal in the AE's pipeline" workflows. |
| Delete Freshsales Contact | Hard-deletes a contact. For GDPR right-to-erasure workflows; for soft removal use a custom "deleted" tag or status field. |
| Delete Freshsales Deal | Removes a deal from the pipeline. For "duplicate deal cleanup" or "lost deal archiving" maintenance workflows. |
| Get Freshsales Contact | Returns a contact by ID with all standard and custom fields plus related deals and activities. The standard lookup before update workflows. |
| Get Freshsales Deal | Returns a deal by ID with value, stage, contacts, activities. The lookup for forecast workflows or for cross-system reporting. |
| List Freshsales Contacts | Paginated contacts with filters. For warehouse-sync workflows, use the updated-since filter for incremental pulls. |
| List Freshsales Deals | Paginated deals with filters by stage, owner, value, recently updated. For pipeline-reporting workflows that aggregate by stage or by owner. |
| Search Freshsales Contacts | Lookup by partial name, email, or other criteria. The standard "find before update" pattern for upsert workflows. |
| Update Freshsales Contact | Partial update — only passed fields change. For enrichment write-back, stage transitions, or external-system sync. |
| Update Freshsales Deal | Updates deal fields — stage, value, owner, expected close date. For "deal moved in external system → reflect in Freshsales" sync workflows. |
Pre-built Freshsales workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Freshsales once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Freshsales field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Freshsales integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Freshsales to Tiny Command?
What Freshsales triggers does Tiny Command support?
What Freshsales actions can I run from a workflow?
Is the Freshsales integration real-time?
Do I need to write code to use Freshsales with Tiny Command?
How much does the Freshsales integration cost?
More crm & sales apps people connect.
Same category as Freshsales, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Freshsales.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
