ActionFreshdeskUpdated September 2026

How do I add a note or reply to a Freshdesk ticket?

Short answer: You can add note to ticket in Freshdesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshdesk Add Note to Ticket action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Add Note to Ticket in Freshdesk — start free All 15 Freshdesk actions

Add Note to Ticket in Freshdesk — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Ticket ID ticket_id	string	Required	Ticket ID. Example: 123
Note Body body	string	Required	HTML content of the note
Visibility private	options	Optional	Visibility. Options: Private (internal note), Public (visible to requester)
Notify Emails notify_emails	string	Optional	Comma-separated email addresses to notify

Sample request

{
  "ticket_id": "e.g. 123",
  "body": "e.g. Hi there, thanks for reaching out.",
  "private": "{{trigger.private}}",
  "notify_emails": "e.g. agent@company.com, manager@company.com"
}

Returns

{
  "id": 1001,
  "body": "Internal update on the issue",
  "private": true,
  "user_id": 456,
  "created_at": "2025-01-15T12:00:00Z"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Add Note to Ticket.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Freshdesk

2 Google Sheets triggers

HubSpot → Freshdesk

18 HubSpot triggers

FAQ

Questions about Add Note to Ticket.

What does the Add Note to Ticket action do in Freshdesk?

Adds a note (private or public) or a reply to an existing Freshdesk ticket. Used for AI-summary notes, automated status updates, or piping context from external systems.

What inputs does Add Note to Ticket require?

Required: Ticket ID, Note Body. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Freshdesk returns an error?

The run history shows the failed step with its input and the error message Freshdesk returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Add Note to Ticket support batch operations?

Run Add Note to Ticket inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Freshdesk's rate limits.

More actions