Who This Is For / When to Use
Use this trigger when workflows need to respond to updates made to notes, such as:
Escalating support issues when notes are revised
Triggering follow-ups after internal status updates
Assigning tasks when notes are modified
Reacting to changes made by sales or support teams
What the Note Changed Trigger Does
When an existing note on a contact is edited:
The contact is added to any workflow using the Note Changed trigger
Filters determine whether the contact is allowed into the workflow
Important
This trigger does not fire when a note is first created
It fires every time a note is edited
Step 1: Create or Open a Workflow
Go to Automations > Workflows.
Click Create Workflow, or open an existing workflow to edit.
Step 2: Add the Note Changed Trigger
In the workflow canvas, click Add New Trigger.
In the trigger list, locate Note Changed under the Contact section and select it.
Step 3: Configure the Trigger
Confirm Trigger Type
Ensure Note Changed is selected under Choose a Workflow Trigger.
Rename the Trigger (Optional)
Update the Workflow Trigger Name if needed.
This name is internal only and does not affect behavior or visibility.
Step 4: Add Filters (Optional)
Filters restrict which contacts are enrolled when a note is edited.
Tag-Based Filters
Has Tag
Only contacts with the selected tag are enrolled.
Doesn’t Have Tag
All contacts are enrolled except those with the selected tag.
Important
Using both filters together can cancel each other out.
Use one or the other, not both.
Custom Field Filters
Limit enrollment to contacts with specific custom field values.
Custom fields must already exist in your account.
Click Save Trigger.
Step 5: Add Workflow Actions
After the trigger, you may add any workflow actions, including:
Send Email
Send SMS
Add or Remove Tags
Assign Tasks
Notify Team Members
Update Contact Fields
You may also leave the workflow without actions if the trigger is only being used for monitoring or logging.
Step 6: Save, Test, and Publish
Click Save in the top-right corner.
Use Test Workflow to validate trigger behavior.
Toggle Publish to activate the workflow.
Common Issues and Fixes
Workflow does not trigger
Confirm the note was edited, not newly added.
Ensure the workflow is Published.
Review filters for unintended exclusions.
Workflow triggers too often
This is expected behavior.
The trigger fires every time a note is edited.
Use conditions, delays, or cooldown logic in actions if needed.
Unexpected contacts enter the workflow
Review tag and custom field filters.
Remove conflicting filter combinations.
Use Cases
Customer Support Task Assignment
Scenario: A support agent updates a note with new issue details.
Trigger Setup:
Trigger: Note Changed
Filter: Has Tag = High Priority
Outcome:
Assigns a task to a senior support specialist
Sends an internal notification
Membership Renewal Reminder
Scenario: A note is updated to indicate an upcoming renewal.
Trigger Setup:
Trigger: Note Changed
Filter: Has Tag = Member
Outcome:
Sends a personalized renewal reminder email
Frequently Asked Questions
What does the Note Changed trigger do?
It starts a workflow whenever an existing note on a contact record is edited.
Does this trigger fire for new notes?
No. It only fires when an existing note is changed.
Can one contact trigger this multiple times?
Yes. The trigger activates each time a note is edited.
Can I rename the trigger?
Yes. The name is internal and does not affect functionality.
Can I filter which contacts are enrolled?
Yes. You can filter by tags or custom field values.
What if multiple note changes happen quickly?
The workflow triggers for each change.
Use delays or conditions to prevent overlapping actions.
How do I ensure the workflow is active?
Confirm the workflow is Saved, Published, and tested using Test Workflow.