Actions are what a workflow does when the trigger fires and all conditions are true. The actions available depend on the field you select; each field type supports certain action types.
For fields that store one value (text, number, yes/no, single choice, assigned user, or date):
For fields that store multiple items (tags, multi-select, connections, locations, communication channels, and similar):
For connection fields that link to another record type:
For the Comments field:
For the Share field (who the record is shared with):
If your site or a plugin provides custom actions, they appear in the action list. One built-in example is Auto-Add People Groups for Groups: when members are added to a group, it can add their people groups to the group’s people group field. Custom actions are configured by the system; you select them like any other action and set the field and value as shown in the design panel.

When you use Add Comment as an action, you can type comment text that includes tokens so Disciple.Tools inserts values from the record. This is useful for noting what changed or for tagging people.
{field_id}. For example {assigned_to} for the Assigned to field.Example: If you type “Hello {assigned_to}, status was updated.” and the Assigned to field is set to a user, the comment will show “Hello @Jane, status was updated.” so that user is notified.
Disciple.Tools runs the actions you defined. If an action would not change anything (for example the field already has that value), the system may skip it to avoid unnecessary updates. Workflow runs are attributed in the activity log so you can see that a change came from a workflow rather than a user.