
Freshservice
Read and write Freshservice tickets, replies and notes, problems, changes, assets, requesters, departments and service requests; read agents, groups and catalog items.
Connect the service desk to monitoring, HR and asset systems so tickets, people and assets stay current without retyping.
Source actions
19
Destination actions
15
Data types
13
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
agents
- Get agentSource
One agent by ID.
- List agentsSource
Agents with roles, groups and departments.
assets
- Create assetDestinationNot retried automatically
Creates an asset of a given asset type.
- Get assetSource
One asset by display ID with its type fields.
- List assetsSource
Assets with type fields, ownership and location.
- Update assetDestinationDuplicate protected
Updates an asset by display ID.
changes
- Create changeDestinationNot retried automatically
Creates a change request with type, risk and planned window.
- Get changeSource
One change request by ID.
- List changesSourceIncremental
Change requests, optionally updated since a time.
- Update changeDestinationDuplicate protected
Updates a change request's fields, status and planned window.
conversations
- List ticket conversationsSource
Replies and notes on a ticket.
departments
- Create departmentDestinationNot retried automatically
Creates a department with optional head, prime user and email domains.
- Get departmentSource
One department by ID.
- List departmentsSource
Departments (companies in MSP mode) with heads and email domains.
- Update departmentDestinationDuplicate protected
Updates a department.
groups
- List agent groupsSource
Agent groups with members, leaders and escalation settings.
notes
- Add ticket noteDestinationNot retried automatically
Adds a note to a ticket; notes are private unless private is false.
problems
- Create problemDestinationNot retried automatically
Creates a problem record.
- Get problemSource
One problem by ID.
- List problemsSource
Problems with priority, impact, status and analysis fields.
- Update problemDestinationDuplicate protected
Updates a problem's fields, status and analysis.
replies
- Reply to ticketDestinationNot retried automatically
Adds a public reply that is emailed to the requester (and any CC or BCC addresses).
requesters
- Create requesterDestinationNot retried automatically
Creates a requester (end user) with contact details and departments.
- Get requesterSource
One requester by ID.
- List requestersSource
Requesters (end users), optionally filtered by email or phone.
- Update requesterDestinationDuplicate protected
Updates a requester's details.
service items
- Get service catalog itemSource
One catalog item by display ID with its request form fields.
- List service catalog itemsSource
Service catalog items, optionally within a category.
service requests
- Place service requestDestinationNot retried automatically
Places a service catalog request for an item on behalf of a requester.
tickets
- Create ticketDestinationNot retried automatically
Creates an incident or service request ticket.
- Get ticketSource
One ticket with optional conversations, requester, stats and related records.
- List ticketsSourceIncremental
Tickets (incidents and service requests), optionally updated since a time.
- Filter ticketsSourceIncremental
Tickets matching status, priority, assignment, tag and date conditions.
- Update ticketDestinationDuplicate protected
Updates ticket fields, status, assignment and custom fields.
Authentication
API key
Plans and access
All Freshservice plans; problems, changes and assets depend on the plan's modules. API keys act with the agent's role and workspace access.
Test environment
A 14-day trial account works; Enterprise plans include a sandbox.
Rate limits
Per-account limits per minute by plan (for example 100 on Starter up to 500 on Enterprise, with per-endpoint sub-limits); HTTP 429 with Retry-After.
Provider events
Workflow Automator webhook actions on ticket, problem, change and asset events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Asset operations use the /api/v2/assets endpoints, which Freshservice documents for accounts created before 31 March 2026; newer Freshservice ITAM accounts use a different asset API that is not covered.
- Problem lists have no updated-since filter; problems are paged in Freshservice's default order.
- Attachments are not uploaded; conversation attachments are returned as metadata only.
- Replies email the requester; notes notify only the listed agents.
- Deleting tickets, problems, changes, assets, requesters and departments is not implemented.
- Creates, replies and notes have no idempotency key; uncertain writes are not repeated automatically.