Freshservice
Raises tickets, reads them and their status, adds notes and closes tickets in one Freshservice workspace, through Freshservice’s API v2. A linked ticket in Plugboard carries Open in Freshservice. It is a ticket connector for one workspace, not two-way synchronisation.
| Category | Ticketing |
| Authentication | API key |
| Reaches | Your Freshservice account, for example https://yourschool.freshservice.com |
| Needs an agent | No |
| Demo mode | No |
Availability
Section titled “Availability”Limited availability. We set this integration up with your team, starting with a pilot at your school, and check it with the provider before you rely on it.
Capabilities
Section titled “Capabilities”ticket.create, ticket.get, ticket.syncStatus, ticket.comment,
ticket.close
- Raise a ticket for the configured requester, in the configured workspace, at low priority and open. It never creates requester accounts.
- Read a ticket and its status. Requester and conversation details are dropped. Every ticket read must match both the ticket asked for and the configured workspace. Open, Pending, Resolved and Closed map to Plugboard statuses; any other status is kept as its own value.
- Add a note. Notes are private unless the note is sent as public, and Freshservice must confirm the visibility that was sent. The workspace is checked first.
- Close a ticket. The workspace is checked first, Freshservice’s own required-field rules apply, and the reply must show the ticket closed.
No attachments, incoming webhooks, comment import, search or custom field mapping. An account that needs custom fields to raise or close a ticket refuses those operations.
Getting the credentials
Section titled “Getting the credentials”- Use an agent whose Freshservice permissions cover only the workspace Plugboard works in. Never an administrator credential that reaches other workspaces or customers.
- Copy that agent’s API key from their Freshservice profile.
- Note the workspace ID, and the ID of an existing requester in that workspace to raise Plugboard’s tickets under.
Configuring it in Plugboard
Section titled “Configuring it in Plugboard”Settings, Connectors, then Freshservice under Add a service, and Continue to setup.
| Field | Value |
|---|---|
baseUrl | The HTTPS address of your Freshservice account, with no path |
workspaceId | The workspace, or MSP client, ID. Never 0, the all-workspaces value |
requesterId | An existing requester in that workspace |
apiKey | The agent’s API key, in the secure credentials |
The connection test reads at most one ticket from the workspace. A pass proves the read was accepted, not that the requester exists or that writes are allowed: raise, note and close a test ticket during the pilot before routing real work to it.
How it behaves
Section titled “How it behaves”- The API key is only ever sent to the configured account address, redirects included.
- Raising a ticket and adding a note are never retried automatically.
- Text is sent as plain text, so a ticket can never inject formatting into Freshservice.
- A reply without a workspace fails rather than assuming one.
See connector configuration for shared setup concepts and the capability reference for the full limits.