[object Object]

Freshworks supports cross-product workflows via the Neo platform. A Freshdesk ticket can spawn a Freshsales activity. A Freshservice change can post a Slack message and update a Freshsales deal. Most teams reach for Zapier first; the native rules are faster, cheaper, and more reliable.

The supported cross-product triggers

  • Freshdesk ticket → Freshsales contact / deal activity
  • Freshservice change → Freshdesk announcement
  • Freshchat conversation closed → Freshsales lead update
  • Freshsales deal won → Freshdesk welcome ticket

Setup at the org level

Cross-product rules require all products to be in the same Freshworks Org. Confirm via Admin → Org Settings. Multi-tenant deployments cannot share workflows directly; use the API instead.

Pattern: Convert won deal to onboarding ticket

When a Freshsales deal hits “Won,” create an onboarding ticket in Freshdesk pre-populated with deal context.

Trigger: Freshsales deal stage = Won
Action:
  Create Freshdesk ticket
    subject: "Welcome - {{deal.name}}"
    requester: deal.primary_contact.email
    custom_fields:
      account_arr: deal.amount
      cs_owner: deal.owner.email

Pattern: VIP ticket → Freshsales activity

When a VIP support ticket comes in, log it on the related Freshsales contact’s timeline. The AE sees it without leaving the CRM.

{
  "trigger": "ticket_created AND requester.tier == VIP",
  "action": "freshsales.create_activity",
  "params": {
    "contact_email": "{{requester.email}}",
    "activity_type": "support_ticket",
    "summary": "{{ticket.subject}} - {{ticket.priority}}"
  }
}

Gotchas

  • Cross-product rules do not retry on transient failure
  • Field mismatches (e.g. priority enum names) cause silent drops
  • Permissions: the rule runs as the system user, not a specific agent
  • Loops are possible (deal → ticket → deal update); add idempotency guards

When to fall back to API

For complex multi-hop logic or external system integration, write a small webhook receiver that does the orchestration. Native rules are best for one-hop, single-product transitions.

What to do this week

List your top three cross-product Zaps, audit if they can be replaced natively, build the won-deal-to-ticket pattern, and add idempotency guards to any loop-prone rule.

[object Object]
Share