Freshdesk automation: rule types, assignment and webhooks

If you have used Freshdesk for a while, you may know these by their old names. Freshdesk used to call them Dispatch'r, Observer and Supervisor, and later brought all three into a single Automations module, with a separate tab for each rule type.

Ticket Creation rules check each new ticket against your conditions and run the actions on a match. You choose whether Freshdesk executes only the first matching rule or all matching rules. With first-match, the order of the list decides which rule wins, so specific rules belong above generic ones.

Ticket Updates is the only rule type where you configure events. A rule needs at least one event and fires when any one of them matches. You also set who performed the action: an agent, the requester, either of them, a collaborator, or the System itself.

• Events: a ticket property changes, an agent or group is updated, a note is added, a reply is sent, customer feedback arrives; system events include failed email delivery and a ticket becoming overdue.
• Conditions: ticket properties (including tags and custom fields), requester contact details and company fields.
• Actions: set fields, reassign agent or group, add tags or watchers, add a note, email an agent, group or requester, mark as spam or delete, or trigger a webhook.

Ticket Updates is also the only rule type that can create a new ticket or add a thread message. The exact list of events depends on your plan and the features you have turned on.

Hourly Triggers don't wait for an event. They scan tickets every hour and act on those that match. That schedule shapes how you write them:

• The time limit you set should be at least one hour, since the rule only runs hourly.
• They count calendar hours, not business hours.
• They only process tickets updated within the last 30 days.
• They work on ticket properties only, not contact or company properties.

Automation rules usually set the group; assignment decides which agent in that group gets the ticket. Freshdesk's automatic assignment runs on its Omniroute engine and offers three methods per group:

• Round-robin: rotates tickets among available agents in the group, skipping agents who are at full capacity and giving the ticket to the eligible agent who was assigned one longest ago.
• Load-balanced: sends each new ticket to the least-loaded agent until every agent reaches the configured maximum. Only tickets with an active SLA timer count toward load, so resolving a ticket or moving it to an SLA-off status frees capacity.
• Skill-based: agents have skills ranked by priority, and a new ticket goes to an agent with the first matching skill. Freshdesk recommends a fallback skill, using the group as the condition, mapped last for all agents so no ticket stays unassigned.

Which methods you can use depends on your plan, so check your group settings before choosing one. Manually assigned tickets still count toward load and can push an agent over the limit, which pauses automatic assignment to them until their count drops.

A webhook in Freshdesk is an automation action that makes an API call to another system. You pick the request type and callback URL, and both the URL and the payload can include placeholders such as {{ticket.id}}. If you make a GET call through a webhook, the rule can't use the response; Freshdesk points to its Trigger API action for that.

Freshdesk executes up to 1,000 webhook calls per hour from automation rules. Calls beyond that are buffered until new capacity is available in the next hour, so high-volume flows should not depend on instant delivery.

For integrations that run outside Freshdesk, use the REST API at your-domain.freshdesk.com/api/v2/. Requests authenticate with your API key as the username and any dummy value as the password. Rate limits are applied per account per minute and depend on your plan; a 429 response means the limit is used up, and the Retry-After header tells you how many seconds to wait. Listing tickets returns only the last 30 days by default, so use the updated_since filter for older tickets.

TascaLab builds on your existing Freshdesk account, with no platform switch, using automation rules, webhooks, the Freshdesk API and Make or n8n where they help. Ticket Routing & Categorization is a one-time project at $775; Custom Automation is from $1,200. Each project includes 30 days of post-launch support and basic documentation, and most setups take 1–3 weeks. A free 30-minute Health Check call is the first step.