Freshservice
IT service management on Freshservice into workflows
Freshservice is the IT service management (ITSM) product in the Freshworks suite — built for IT teams managing tickets, change requests, problems, releases, and assets across the corporate environment. Seven actions cover the operational surface: Create Ticket, Get Ticket, List Tickets, Delete Ticket, Add Note (internal or public), List Agents. No native triggers today (Freshservice's webhook system is configured per-rule in their automation builder; native triggers ship in the next release). The integration uses a Freshservice API key from your agent profile. Common patterns: a Datadog alert fires a workflow that creates the matching Freshservice ticket with the right priority and assigned group based on the alert source; or a new Workday employee record auto-creates an onboarding ticket with subtasks for equipment provisioning, account creation, and welcome documentation.
Do anything Freshservice 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 |
|---|---|
| Add Note to Freshservice Ticket | Posts a public reply or private note to a ticket. Useful for "AI-summarised context → log as private note for the agent" patterns. |
| Create Freshservice Ticket | Files a new IT ticket with subject, description, priority, requester, group. For "monitoring alert → auto-file ticket for the on-call team" or "user submitted via portal → create ticket" workflows. |
| Delete Freshservice Ticket | Removes a ticket (soft delete in most configurations). For "duplicate ticket cleanup" or "spam filtering" maintenance workflows. |
| Get Freshservice Ticket | Returns a ticket by ID with full detail — status, requester, agent, conversation history, custom fields. The standard lookup for ticket-context workflows. |
| List Freshservice Agents | Returns every agent with role, group memberships, contact info. Useful for resolving agent IDs in routing rules or for "show me agents currently on shift" workflows. |
| List Freshservice Tickets | Paginated tickets with filters by status, priority, requester, agent, group, time range. For "open critical tickets" dashboards or "all tickets I'm the agent on" personal queues. |
| Update Freshservice Ticket | Partial update on ticket fields — status, priority, assignee, custom fields. For "auto-route to the right team based on subject keywords" workflows or for "auto-resolve aged tickets" maintenance. |
Pre-built Freshservice workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Freshservice event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Freshservice into a Notion-backed source of truth, auto-tagged.
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 Freshservice once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Freshservice 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 Freshservice integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Freshservice to Tiny Command?
What Freshservice triggers does Tiny Command support?
What Freshservice actions can I run from a workflow?
Is the Freshservice integration real-time?
Do I need to write code to use Freshservice with Tiny Command?
How much does the Freshservice integration cost?
More other apps people connect.
Same category as Freshservice, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Freshservice.
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.
