How to add note to freshservice ticket in Freshservice

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add Note to Freshservice Ticket support batch operations?

Yes. Run Add Note to Freshservice Ticket inside a Loop node to process arrays. TinyCommand handles Freshservice's rate limits automatically so you don't have to throttle manually.

More actions