A new workflow action called Log Comment lets administrators automatically post comments on records when a workflow's conditions are met. The comment supports formatted text, dynamic field tokens (like the account name), and -mentions of users and groups — exactly like a manually posted comment. Tagged people receive the same email, web, and SMS notifications they would from a normal-
mention.
1. Before You Start
You will need:
An administrator account in the CRM (the Workflows area is admin-only).
A workflow already created, or permission to create one.
A target module that supports comments — for example Accounts, Leads, Contacts, Intake Opportunities, or Project. Modules whose comments attach to a parent record (such as Tasks) are also supported; the comment is posted on the parent.
Access requirements: the Log Comment action shows up automatically in the Action Type dropdown for any module where comments are enabled. No feature flag toggle is required.
If you don't see Log Comment in the Add Action menu, the new workflow task type may not yet be registered on your instance. Contact Dazos so they can run the one-support and reference time setup. CRM-2918
2. Open the Workflow Editor
From the CRM:
1. Click your profile picture (top-right) → Settings → CRM Settings.
2. In the left sidebar choose Automations → Workflows.
3. Either click Add Workflow to start a fresh one, or click an existing workflow to edit it.
4. Pick the Target Module (the module whose records should trigger the workflow), set the trigger condition (Every time the record is saved, Only on the first save, etc.), and add any filter conditions you need.
Once the target module and trigger are saved, the Actions area appears at the bottom of the editor.
3. Add the Log Comment Action
In the Actions area:
1. Click Add Action.
2. From the action-type dropdown choose Log Comment.
3. The Log Comment configuration form opens.
Field | Description | Example |
Action Title | A short label that identifies this action in the workflow's action list. | Notify clinical team |
Comment Message | The body of the comment. Supports rich text, field tokens, and @ -mentions. | New referral for $accountname$ — please review. |
Add Field | Picker that drops dynamic record values (tokens) into the message at the cursor. | $accountname$ , $assigned_user_id$ |
Comment Creator | Who appears as the comment's author. Leave blank to use the user who triggered the workflow. | Specific User or Owner Field on Record |
4. Write the Comment Message
Three ways to compose the message:
a) Type plain or formatted text. Use the toolbar for bold, italic, lists, links, etc.
b) Insert a dynamic field token. Use the Add Field dropdown on the right of the editor. Pick a field (for example, ) and the matching token is inserted at the cursor. When the workflow runs, the token is replaced with the record's current value.
Token | Becomes (at run time) |
$accountname$ | The Account's name on the target record. |
$assigned_user_id$ | The Assigned To user's name. |
$(account_id : (Accounts) primary_email) | A chained value — the linked Account's primary email. |
c) Tag a user or group by typing. Inside the editor, type the @ character and a small list of users and groups appears. Click one @ to insert a tag.
5. Choose the Comment Creator
Comment Creator controls who appears as the author of the comment when the workflow posts it.
Choice | Behaviour |
(leave blank) | The user whose action triggered the workflow becomes the comment author. This is usually what you want. |
Specific User | Pick one person or one group from the second picklist. If you pick a group, the comment is authored by the group's first member (because a comment is owned by exactly one user). |
Owner Field on Record | Pick an Owner-type field (e.g. Assigned To, Sales Rep, Closing Agent) on the target record — or even a parent record. The user currently in that field becomes the author. |
When you choose Specific User or Owner Field on Record, a second picklist slides into view next to the first.
For Owner Field on Record, the second picklist offers two kinds of options:
● Direct fields on the target module — for example Account Name : Closing Agent Account Name : Sales Rep , Accou
● Chained fields through a parent reference — for example closing agent on the Account the target record links to, and so on. )
6. Save and Activate the Workflow
1. Click Save on the Log Comment action.
2. The action appears in the workflow's Actions list, showing the Action Title you set and an ON/OFF toggle.
3. Make sure the workflow itself is Active (top of the editor) and click Save on the workflow.
You can repeat the process to add several Log Comment actions on the same workflow — each will post its own comment when the trigger fires.
7. How It Behaves at Run Time
When the workflow's trigger conditions match a record:
Step | What happens |
Field tokens | Replaced with the record's current values (e.g. $accountname$ becomes the actual account name). |
Typed @ - mentions | Preserved exactly as you composed them. |
Owner-field creator | Looked up at the moment the workflow fires — so if Sales Rep changes between configuration and run, the comment is authored by the current Sales Rep. |
Group creator | Expanded to the group's first member; the rest of the group is not mentioned unless you tagged them in the body. |
Comment record | Saved on the target record. For child modules whose comments live on a parent (such as Tasks), the comment is saved on the parent. |
Notifications | Email, web push, and SMS dispatched to every tagged user according to their notification preferences. |
Further workflows | A workflow targeting ModComments will still fire on this new comment, exactly like a manualcomment post. |
