Skip to content
All connectors
Freshservice logo

Freshservice

Software delivery, ITSM & observability

Turn incidents and requests into Freshservice work items, and keep status in step across your tools.

45 ways to read, 25 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Freshservice with Nexra

Connected, approved, proven.

The things teams do most with Freshservice, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create assetassets.createApproval by rule
  • Add change notechange_notes.createApproval by rule
  • List agentsagents.listRead

Example flow

  1. Freshservice · List agentsagents.listDone
  2. Freshservice · Create assetassets.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Freshservice.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Freshservice
  • Freshservice's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

For developers

Technical detail

Freshservice tickets, problems, changes, releases, tasks, notes, assets, requesters, departments and service requests; read approvals, time, people, catalog and knowledge.

Freshworks API docs
Source actions
45
Destination actions
25
Data types
36

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

agents2
  • Get agentSource

    One agent by ID.

  • List agentsSource

    Agents with roles, groups and departments.

asset components1
  • List asset componentsSource

    Hardware and software components discovered on an asset.

asset types1
  • List asset typesSource

    Asset types and their parent types.

assets4
  • Create assetDestinationNot retried automaticallyApproval before production

    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 assetDestinationProvider duplicate protectionApproval before production

    Updates an asset by display ID.

change approvals1
  • List change approvalsSource

    Approvals requested on a change with approver, level and status. Read only: Nexra never approves, rejects or requests approval.

change notes2
  • Add change noteDestinationNot retried automaticallyApproval before production

    Adds an internal note to a change. Nobody is emailed: notify_emails is never sent.

  • List change notesSource

    Internal notes on a change.

change tasks2
  • Create change taskDestinationNot retried automaticallyApproval before production

    Creates an open or in-progress task on a change. It never changes the change itself.

  • List change tasksSource

    Tasks on a change with assignee, status and due date.

changes4
  • Create changeDestinationNot retried automaticallyApproval before production

    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 changeDestinationProvider duplicate protectionApproval before production

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

conversations1
  • List ticket conversationsSource

    Replies and notes on a ticket.

departments4
  • Create departmentDestinationNot retried automaticallyApproval before production

    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 departmentDestinationProvider duplicate protectionApproval before production

    Updates a department.

groups2
  • Get agent groupSource

    One agent group with members, leaders and observers.

  • List agent groupsSource

    Agent groups with members, leaders and escalation settings.

locations2
  • Get locationSource

    One location by ID.

  • List locationsSource

    Locations with address and parent location.

notes1
  • Add ticket noteDestinationNot retried automaticallyApproval before production

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

private notes1
  • Add private ticket noteDestinationNot retried automaticallyApproval before production

    Adds a private note to a ticket. It is always private and never notifies anyone by email; use this instead of notes.create for internal updates.

problem notes2
  • Add problem noteDestinationNot retried automaticallyApproval before production

    Adds an internal note to a problem. Nobody is emailed: notify_emails is never sent.

  • List problem notesSource

    Internal notes on a problem.

problem tasks2
  • Create problem taskDestinationNot retried automaticallyApproval before production

    Creates an open or in-progress task on a problem. It never changes the problem itself.

  • List problem tasksSource

    Tasks on a problem with assignee, status and due date.

problems4
  • Create problemDestinationNot retried automaticallyApproval before production

    Creates a problem record.

  • Get problemSource

    One problem by ID.

  • List problemsSource

    Problems with priority, impact, status and analysis fields.

  • Update problemDestinationProvider duplicate protectionApproval before production

    Updates a problem's fields, status and analysis.

products1
  • List productsSource

    Products in the product catalog with asset type and procurement mode.

release notes2
  • Add release noteDestinationNot retried automaticallyApproval before production

    Adds an internal note to a release. Nobody is emailed: notify_emails is never sent.

  • List release notesSource

    Internal notes on a release.

release tasks2
  • Create release taskDestinationNot retried automaticallyApproval before production

    Creates an open or in-progress task on a release. It never changes the release itself.

  • List release tasksSource

    Tasks on a release with assignee, status and due date.

releases4
  • Create releaseDestinationNot retried automaticallyApproval before production

    Creates a release that is open, on hold, in progress or incomplete.

  • Get releaseSource

    One release by ID.

  • List releasesSource

    Releases with type, planned and actual windows, and linked changes.

  • Update releaseDestinationProvider duplicate protectionApproval before production

    Updates a release's fields and planned window without completing it.

replies1
  • Reply to ticketDestinationNot retried automaticallyApproval before production

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

requested items1
  • List requested itemsSource

    Catalog items requested on a service request ticket, with stage and quantity.

requester groups1
  • List requester groupsSource

    Requester groups (manual or rule based).

requesters4
  • Create requesterDestinationNot retried automaticallyApproval before production

    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 requesterDestinationProvider duplicate protectionApproval before production

    Updates a requester's details.

roles1
  • List agent rolesSource

    Agent roles with their module scopes. Read only: roles are never assigned or changed.

service categories1
  • List service catalog categoriesSource

    Service catalog categories with position and parent.

service items2
  • 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 requests1
  • Place service requestDestinationNot retried automaticallyApproval before production

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

solution articles2
  • Get solution articleSource

    One knowledge base article with its body.

  • List solution articlesSource

    Knowledge base articles in a folder.

solution categories1
  • List solution categoriesSource

    Knowledge base (solutions) categories.

solution folders1
  • List solution foldersSource

    Knowledge base folders, optionally within one category.

ticket tasks2
  • Create ticket taskDestinationNot retried automaticallyApproval before production

    Creates an open or in-progress task on a ticket. It never changes the ticket itself.

  • List ticket tasksSource

    Tasks on a ticket with assignee, status and due date.

tickets5
  • Create ticketDestinationNot retried automaticallyApproval before production

    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 ticketDestinationProvider duplicate protectionApproval before production

    Updates ticket fields, status, assignment and custom fields.

time entries1
  • List ticket time entriesSource

    Time logged on a ticket, with agent, billable flag and time spent.

vendors1
  • List vendorsSource

    Vendors with address and primary contact.

Access and limits

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.
Pagination
page and per_page (up to 100) with a Link rel="next" header; ticket filters return 30 per page with a total.
Provider events
Workflow Automator webhook actions on ticket, problem, change and asset events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Nothing is deleted or merged, and no added operation emails requesters: added notes are private or internal with no notify list, and added task and release writes never close or complete the parent.
  • Changes are never sent for approval, approved or closed by added operations; change approvals are read only.
  • Release and task status names follow the API reference; required release create fields are not marked in the reference, so subject, priority, status, type and the planned window are required to match the documented example.
  • 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.

Developer reference

  1. Create the Freshworks credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Freshservice, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/freshservice and the Connections API.