ActionFreshserviceUpdated September 2026

How do I add a note to a Freshservice ticket?

Short answer: You can add note to freshservice ticket in Freshservice by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshservice Add Note to Freshservice Ticket action to a workflow, map its 3 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 Freshservice Ticket in Freshservice — start free All 7 Freshservice actions

Add Note to Freshservice Ticket in Freshservice — 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	Message body content. Plain text unless the API specifies HTML/markdown.
Visibility private	options	Optional	Visibility. Options: Private (internal), Public

Sample request

{
  "ticket_id": "e.g. 123",
  "body": "e.g. Hi there, thanks for reaching out.",
  "private": "{{trigger.private}}"
}

Returns

{
  "conversation": {
    "id": 1001,
    "body": "Note content",
    "private": true
  }
}

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 Freshservice Ticket.

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

Google Sheets → Freshservice

2 Google Sheets triggers

HubSpot → Freshservice

18 HubSpot triggers

FAQ

Questions about Add Note to Freshservice Ticket.

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

Posts a public reply or private note to a ticket. Useful for "AI-summarised context → log as private note for the agent" patterns.

What inputs does Add Note to Freshservice 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 Freshservice returns an error?

The run history shows the failed step with its input and the error message Freshservice 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 Freshservice Ticket support batch operations?

Run Add Note to Freshservice 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 Freshservice's rate limits.

More actions