ActionFrontUpdated September 2026

How do I add a Front internal comment?

Short answer: You can add front internal comment in Front by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Front Add Front Internal Comment 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 Front Internal Comment in Front — start free All 3 Front actions

Add Front Internal Comment in Front — 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
Conversation ID conversation_id	string	Required	The Conversation ID assigned by Front. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Author Teammate ID author_id	string	Required	–
Comment Body body	string	Required	Message body content. Plain text unless the API specifies HTML/markdown.

Sample request

{
  "conversation_id": "{{trigger.conversation_id}}",
  "author_id": "{{trigger.author_id}}",
  "body": "e.g. Hi there, thanks for reaching out."
}

Returns

{
  "id": "com_abc",
  "body": "..."
}

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

Triggered by

Apps that pair well as the trigger for Add Front Internal Comment.

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

Google Sheets → Front

2 Google Sheets triggers

HubSpot → Front

18 HubSpot triggers

FAQ

Questions about Add Front Internal Comment.

What does the Add Front Internal Comment action do in Front?

Posts an internal team note on a conversation thread — visible to teammates only, not the customer. For "AI-summarised CRM context → log as internal note before the agent replies" workflows.

What inputs does Add Front Internal Comment require?

Required: Conversation ID, Author Teammate ID, Comment 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 Front returns an error?

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

Run Add Front Internal Comment 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 Front's rate limits.

More actions

Other Front actions.

Action

Reply to Front Conversation

Posts a customer-facing reply via the conversation's original channel (email, SMS, social DM). For "approved auto-response from a Slack thumbs-up → reply to the customer" patterns.

Action

Update Front Conversation

Changes conversation state — status, assignee, inbox, tags. For "auto-route by content category" workflows or for "auto-close idle conversations" maintenance.

Add Front Internal Comment in Front — start free