Freshdesk
Freshdesk is a helpdesk: customer tickets, the contacts who raise them, the companies they belong to, and the agents who answer.
Authentication
- API key
Actions
Generic API request. Call any Freshdesk API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.
- Add note (v1)Add a note to a ticket (POST /tickets/{id}/notes).
- Add reply (v1)Reply to a ticket, emailing the requester (POST /tickets/{id}/reply).
- Create contact (v1)Create a requester (contact) in the connected Freshdesk helpdesk, so tickets can be raised against a known person rather than a bare email.
- Create ticket (v1)Create a new ticket (POST /tickets).
- Delete ticket (v1)DestructiveDelete a ticket by id (DELETE /tickets/{id}).
- Get ticket (v1)Retrieve one Freshdesk ticket by its numeric id, to read its current subject, status, priority and requester before replying to or escalating it.
- List agents (v1)List agents in the Freshdesk account with optional pagination (GET /agents).
- List companies (v1)List companies in the Freshdesk account with optional pagination (GET /companies).
- List contacts (v1)List contacts with optional filtering and pagination (GET /contacts).
- List tickets (v1)List tickets with optional filtering and pagination (GET /tickets).
- Update contact (v1)DestructiveUpdate fields on an existing Freshdesk contact.
- Update ticket (v1)DestructiveUpdate fields on an existing ticket (PUT /tickets/{id}).
Triggers
- Customer message received (webhook)Starts the instant a customer opens a ticket or replies on one in Freshdesk, delivered by a webhook your Freshdesk automation rules send.
- Customer messages on ticketsAnswers as an agent in Freshdesk: when a customer opens a ticket or replies on one, the agent posts a public reply on that ticket.
- New or updated ticketStarts when a Freshdesk ticket is created or updated.
Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.