All connectors
Implemented
Software delivery, ITSM & observability
Freshservice logo

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 agent
    Source

    One agent by ID.

  • List agents
    Source

    Agents with roles, groups and departments.

assets
  • Create asset
    Destination
    Not retried automatically

    Creates an asset of a given asset type.

  • Get asset
    Source

    One asset by display ID with its type fields.

  • List assets
    Source

    Assets with type fields, ownership and location.

  • Update asset
    Destination
    Duplicate protected

    Updates an asset by display ID.

changes
  • Create change
    Destination
    Not retried automatically

    Creates a change request with type, risk and planned window.

  • Get change
    Source

    One change request by ID.

  • List changes
    Source
    Incremental

    Change requests, optionally updated since a time.

  • Update change
    Destination
    Duplicate protected

    Updates a change request's fields, status and planned window.

conversations
  • List ticket conversations
    Source

    Replies and notes on a ticket.

departments
  • Create department
    Destination
    Not retried automatically

    Creates a department with optional head, prime user and email domains.

  • Get department
    Source

    One department by ID.

  • List departments
    Source

    Departments (companies in MSP mode) with heads and email domains.

  • Update department
    Destination
    Duplicate protected

    Updates a department.

groups
  • List agent groups
    Source

    Agent groups with members, leaders and escalation settings.

notes
  • Add ticket note
    Destination
    Not retried automatically

    Adds a note to a ticket; notes are private unless private is false.

problems
  • Create problem
    Destination
    Not retried automatically

    Creates a problem record.

  • Get problem
    Source

    One problem by ID.

  • List problems
    Source

    Problems with priority, impact, status and analysis fields.

  • Update problem
    Destination
    Duplicate protected

    Updates a problem's fields, status and analysis.

replies
  • Reply to ticket
    Destination
    Not retried automatically

    Adds a public reply that is emailed to the requester (and any CC or BCC addresses).

requesters
  • Create requester
    Destination
    Not retried automatically

    Creates a requester (end user) with contact details and departments.

  • Get requester
    Source

    One requester by ID.

  • List requesters
    Source

    Requesters (end users), optionally filtered by email or phone.

  • Update requester
    Destination
    Duplicate protected

    Updates a requester's details.

service items
  • Get service catalog item
    Source

    One catalog item by display ID with its request form fields.

  • List service catalog items
    Source

    Service catalog items, optionally within a category.

service requests
  • Place service request
    Destination
    Not retried automatically

    Places a service catalog request for an item on behalf of a requester.

tickets
  • Create ticket
    Destination
    Not retried automatically

    Creates an incident or service request ticket.

  • Get ticket
    Source

    One ticket with optional conversations, requester, stats and related records.

  • List tickets
    Source
    Incremental

    Tickets (incidents and service requests), optionally updated since a time.

  • Filter tickets
    Source
    Incremental

    Tickets matching status, priority, assignment, tag and date conditions.

  • Update ticket
    Destination
    Duplicate 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.