Module Actions

The Actions tab lets you define custom actions that users can trigger on module records. Actions appear in the grid toolbar, record views, and bulk selection menus.

What are Module Actions?

Actions are buttons that perform operations on records. While Coherence provides built-in actions (edit, delete, duplicate), custom actions let you create specialized workflows:

Convert a Lead to a Person
Change a Deal's status to "Won"
Trigger an automation workflow
Perform bulk operations on selected records

Accessing the Actions Tab

Go to Settings > Modules
Select your module
Click the Actions tab

Action Types

Coherence supports four types of custom actions:

Record Conversion

Transform records from one module to another.

Setting	Description
Target Module	Which module to create the new record in
Field Mapping	How fields map from source to target (JSON)
Mark Source As	Optionally update source record status after conversion

Use cases:

Lead → Person (after qualification)
Quote → Invoice (after acceptance)
Candidate → Employee (after hiring)

Example field mapping:

{
  "name": "full_name",
  "email": "work_email",
  "company": "organization"
}

Status Transition

Update a record's status field with a single click.

Setting	Description
Target Status	The status value to set

Use cases:

Mark as Won/Lost
Archive record
Approve/Reject
Complete task

Bulk Operation

Perform operations on multiple selected records at once.

Use cases:

Assign to user
Add tags
Update field values
Delete selected

Automation Trigger

Fire an event that automation workflows can respond to.

Setting	Description
Event Name	The event identifier for automations

Use cases:

Request approval
Send notification
Trigger external integration
Start multi-step workflow

Creating an Action

Click Add Action in the Actions tab
Configure the action settings

Basic Settings

Setting	Description
Label	Button text (e.g., "Convert to Contact")
Icon	Visual icon for the button
Display	How to show: Icon + Text, Icon Only, or Text Only
Action Type	The type of action (see above)

Visibility Settings

Control where the action appears:

Setting	Description
Show in Grid Toolbar	Display above the record list
Show in Record View	Display on individual record pages
Show in Bulk Selection Menu	Display when records are selected
Enabled	Toggle action on/off without deleting

Click Create to save the action

Managing Actions

Editing Actions

Find the action in the list
Click the pencil icon
Update settings
Click Save

Deleting Actions

Find the action to remove
Click the trash icon
Confirm deletion

Deleting an action is permanent and cannot be undone.

Disabling Actions

To temporarily hide an action without deleting it:

Edit the action
Toggle Enabled off
Save

Disabled actions show a "Disabled" badge in the list.

Action Display

Each action in the list shows:

Icon - Visual representation
Label - Action name
Type - Record Conversion, Status Transition, etc.
Visibility - Where it appears (Grid, Record, Bulk)
Status - Enabled or Disabled

Example Configurations

Convert Lead to Contact

Setting	Value
Label	Convert to Contact
Icon	User Plus
Type	Record Conversion
Target Module	Contacts
Field Mapping	`{"name": "full_name", "email": "email"}`
Mark Source As	converted
Show in Record View	Yes
Show in Grid Toolbar	No
Show in Bulk Menu	No

Mark Deal as Won

Setting	Value
Label	Mark as Won
Icon	Check Circle
Type	Status Transition
Target Status	won
Show in Record View	Yes
Show in Grid Toolbar	Yes
Show in Bulk Menu	Yes

Request Approval

Setting	Value
Label	Request Approval
Icon	Send
Type	Automation Trigger
Event Name	approval-requested
Show in Record View	Yes
Show in Grid Toolbar	No
Show in Bulk Menu	No

Best Practices

Name Actions Clearly

Use verb phrases that describe what happens:

✅ "Convert to Contact", "Mark as Complete", "Request Approval"
❌ "Action 1", "Process", "Do"

Choose Appropriate Visibility

Single-record actions (Convert, Approve): Show in Record View
Bulk actions (Assign, Tag): Show in Bulk Menu
Common actions (Status changes): Show in Grid Toolbar

Consider the Workflow

Think about when users need actions:

Conversion typically happens after reviewing a record
Status changes may happen from list or detail view
Automation triggers usually need record context

Test Before Publishing

Create test records and verify:

Action appears in the right places
Field mappings work correctly
Status transitions update properly
Automation events fire correctly