Short answer: Drop the "Freshdesk → Add Note to Ticket" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"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"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.