[object Object]

Workflow Rules

Trigger on record create, update, field change, and time-based conditions. Available actions include update fields on the same record, update fields on related records (account fields from a deal trigger), assign owner via round-robin, send template email, create a task, create a follow-up activity, and call a webhook. Configure under Admin -> Automations -> Workflows. Rules execute in priority order — set explicit priorities rather than relying on creation order, because priority survives renames and moves while creation order is fragile.

// Webhook payload Freshsales sends to your endpoint on deal stage change
{
  "event_name": "Deal Updated",
  "data": {
    "deal": {
      "id": 901234,
      "name": "Acme Renewal 2026",
      "deal_stage_id": 5,
      "amount": 48000,
      "currency": "USD",
      "owner_id": 7,
      "updated_at": "2026-04-24T11:32:00Z"
    },
    "previous": { "deal_stage_id": 4 }
  }
}

Email Sequences

Multi-step automated outreach per prospect. Define touch cadence (Day 1 email A, Day 3 email B, Day 7 LinkedIn task, Day 10 email C). Branch on opens, clicks, and replies. Pause automatically on reply detection so a hand-raised prospect doesn’t get touch 4 the morning after they responded. Avoid email-only sequences; the sequences that perform best mix email with calls and LinkedIn tasks because the channel mix matches how buyers actually respond. Available on Pro+ tiers.

Sales Cadence

A structured plan of touches across a defined period — typically 21 days for outbound prospecting, 30-60 days for nurture, 14 days for inbound follow-up. Reps follow the cadence; the system reminds of overdue steps via the Today view. Cadence templates live in the Sequences module. Customize per persona (developers respond differently than VPs), per region (timezone-aware send windows), per product line. The cadence library is a living artifact — review monthly with sales ops to retire underperformers and promote winners.

Custom Actions

Webhooks into Freshworks Marketplace apps or your own endpoints extend beyond built-in actions. Common custom actions: post a Slack message to the deal channel on stage change, push a closed-won deal to a billing system (Stripe, Chargebee, NetSuite), enrich a new lead via Clearbit and write back the company size and tech stack, trigger a Zapier or Make workflow for the long tail of integrations. Webhook payloads include the full record and the change diff, so the receiving endpoint doesn’t need to re-query.

Observability

The Activity Timeline on each record shows automations that fired, in chronological order, with timestamps and outcome. The Workflow Logs view (Admin -> Automations -> Workflow Logs) shows aggregate performance: fire count, success/failure ratio, and the most recent failure message per rule. Build reports on sequence performance — open rate, reply rate, meeting booked rate per sequence. Disable underperformers, don’t hide them; deletion loses the audit trail.

Common Failure Modes

Three. First, infinite loops between two workflow rules where rule A updates field X (triggering rule B), and rule B updates field Y (triggering rule A). Use the “skip workflow if triggered by workflow” option to break the cycle. Second, sequences that send during weekends and holidays; configure send windows per sequence and respect the recipient’s timezone, not the sender’s. Third, webhook timeouts — your endpoint must respond within 5 seconds or Freshsales retries with exponential backoff up to 4 times then drops the event; do the heavy work async and return 200 fast.

Implementation Sequence

Build workflows in this order: data hygiene first (auto-fill missing fields, normalize values), notification next (alert reps to changes that need attention), then automation (multi-step routing and creation). Reverse order is tempting but creates messes — automating creation before normalizing values produces records full of bad data.

What to do this week

Audit your sequences by reply rate. Anything below 3% reply rate after 100 sends is wasting deliverability. Pause and rewrite, or kill outright.

[object Object]
Share