REVSET LABS · EXPERT GUIDE·Automation & Workflows

Mastering Exact Match & Contains Phrase Workflow Triggers in GHL

1,285 words·5 min read·Updated 28 April 2026·beginner·

Arsalan ZaffarLinkedIn

👉 Start your 30-day GoHighLevel free trial.

Quick Answer

To configure a workflow trigger with exact match or contains phrase logic, go to Automation → Workflows. Select an existing workflow or create a new one, then click Add new Workflow Trigger. Configure the filter condition using the 'is' operator for exact match or the 'contains' operator for partial matches. This process typically takes 5-10 minutes.

Key Takeaways

✓Always test your workflow triggers thoroughly after creation to ensure they fire correctly.
✓Use 'is' for specific, unambiguous values like unique tags or exact custom field entries.
✓Choose 'contains' for broader matching, such as keywords within longer text fields or notes.
✓Be mindful of case sensitivity; GHL triggers are generally case-sensitive for text comparisons.
✓Regularly review and refine your workflow triggers to prevent unintended automations or missed opportunities.

Understanding Workflow Trigger Logic in GoHighLevel

GoHighLevel workflows are powerful automation tools that rely on triggers to initiate sequences of actions. Understanding how to set up these triggers precisely is crucial for effective automation. This guide focuses on using 'exact match' and 'contains phrase' conditions, which dictate when your workflows start based on specific data.

🔥 Pro Tip

Always map out your desired automation path before building the trigger. This ensures you select the correct data points and logic operators for your specific needs.

What is 'Exact Match' vs. 'Contains Phrase'?

The primary difference between 'exact match' and 'contains phrase' lies in their strictness when evaluating data. Choosing the right operator prevents your workflows from firing incorrectly or failing to fire when needed. Let's explore each concept to clarify their best use cases.

Define 'Exact Match' ('is' operator) — An 'exact match' condition requires the data in a field to be precisely identical to the value you specify. For example, if you set a trigger for 'Contact Tag is New Lead', the workflow only fires when the tag is *exactly* 'New Lead', not 'new lead' or 'New Lead - Website'.

Define 'Contains Phrase' ('contains' operator) — A 'contains phrase' condition looks for the presence of a specified text string anywhere within a field's value. For instance, if you set a trigger for 'Custom Field contains website', the workflow fires if the field's value is 'Visited website', 'website inquiry', or 'Signed up on our website'.

When to Use Each Operator — Use 'is' for unique identifiers like specific contact tags, precise custom field selections, or exact form submission values. Use 'contains' for broader matching, such as keywords in notes, email subjects, or text fields where variations might exist.

✅ Choosing the correct operator is the most critical decision for accurate workflow execution. A mismatch here leads to automation errors.

How to Create an Exact Match Workflow Trigger

Setting up an exact match trigger ensures your workflows activate only when specific conditions are met without any ambiguity. This method is ideal for highly precise automations, such as when a contact receives a particular tag or a custom field has a definite value.

Navigate to Workflows — From your GoHighLevel dashboard, click Automation in the left sidebar. Then, select Workflows to view your existing automation sequences.

Create or Edit a Workflow — Click + Create workflow to start a new automation from scratch, or select an existing workflow to add a new trigger to it. If creating new, choose Start from Scratch and click Create New Workflow.

Add a New Workflow Trigger — Inside your workflow, click + Add new Workflow Trigger at the top. This opens a panel where you can select the event that starts your automation.

Select a Trigger Type — Search for and select your desired trigger type from the list, such as Contact Tag, Custom Field Updated, or Form Submitted. The available conditions will vary based on the trigger chosen.

Configure the Exact Match Condition — For a Contact Tag trigger, select 'Contact Tag' in the filter section, then choose the operator is from the dropdown. Type the *exact* tag name, like 'New Lead', into the value field. For a Custom Field Updated trigger, select the custom field, choose is, and enter the exact value you expect.

Add Additional Filters (Optional) — You can add more conditions using the + Add Filter button. For example, you might add 'Contact Type is Lead' to refine your trigger further. Ensure the logic (AND/OR) matches your intent.

Save the Trigger and Workflow — Click Save Trigger to apply your settings. Then, remember to click Save at the top right of the workflow builder and set the workflow to Publish to make it active.

⚠️ Exact match triggers are case-sensitive. 'new lead' is different from 'New Lead'. Always verify the exact casing of your data.

🔥 Pro Tip

For exact match triggers based on custom fields, consider using dropdown or radio button field types. This eliminates user input errors and guarantees exact values for your triggers.

Try GoHighLevel Free

Start your 30-day GoHighLevel free trial

Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.

Start 30-Day Free Trial →

Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.

How to Use 'Contains Phrase' in Workflow Triggers

The 'contains phrase' condition offers more flexibility, allowing a workflow to fire if a specific text string is present anywhere within a field's value. This is highly useful for capturing variations in user input or detecting keywords within longer text entries.

Access Workflow Trigger Settings — Follow steps 1-3 from the 'Create an Exact Match Workflow Trigger' section to navigate to your workflow and add a new trigger. This ensures you are in the correct configuration area.

Select a Trigger Type — Choose a trigger type that involves text-based data, such as Custom Field Updated, Form Submitted, or Contact Created. The 'contains' operator is most effective with text fields.

Configure the 'Contains Phrase' Condition — For a Custom Field Updated trigger, select your custom field and choose the operator contains from the dropdown. Then, type the phrase you want to match, such as 'demo request', into the value field. The workflow will fire if the custom field's content includes 'demo request' anywhere.

Consider Case Sensitivity and Partial Matches — Remember that 'contains' is typically case-sensitive. 'demo' is different from 'Demo'. Also, a partial match like 'web' will trigger for 'website', 'webinar', and 'webpage'.

Add Multiple 'Contains' Conditions (Optional) — You can add multiple 'contains' filters using + Add Filter. For instance, 'Custom Field contains demo' AND 'Custom Field contains booked' would only trigger if both phrases are present in the field.

Save and Publish Your Workflow — Click Save Trigger to apply your changes. Finally, Save the entire workflow and ensure it is set to Publish to activate the automation.

⚠️ Be careful with broad 'contains' phrases. A short, common word might trigger your workflow too often or for irrelevant contacts. Test thoroughly.

🔥 Pro Tip

When using 'contains', consider common misspellings or variations of your target phrase. You might need multiple 'contains' conditions with an OR logic to capture all possibilities (e.g., 'contains demo' OR 'contains DMO').

Advanced Workflow Trigger Scenarios

GoHighLevel allows you to combine multiple conditions within a single workflow trigger, enabling highly sophisticated automation logic. By understanding AND/OR operators, you can build triggers that cater to complex business rules, ensuring your workflows activate only under precise circumstances.

Combine 'Exact Match' and 'Contains Phrase' — You can use both 'is' and 'contains' operators within the same trigger by adding multiple filters. For example, 'Contact Tag is VIP' AND 'Custom Field contains product interest' could be a powerful combination.

Utilize AND/OR Logic — When adding multiple filters, GoHighLevel defaults to 'AND' logic, meaning all conditions must be true. Click on the 'AND' operator to change it to 'OR' if you want the workflow to fire when *any* of the conditions are met. Grouping conditions effectively is key.

Example: Tag AND Custom Field Contains — Imagine a trigger: 'Contact Tag is 'New Lead'' AND 'Custom Field 'Interest' contains 'Marketing''. This workflow only fires for new leads specifically interested in marketing. This ensures targeted follow-up.

Example: Custom Field Is OR Another Custom Field Contains — Consider a trigger: 'Custom Field 'Source' is 'Website'' OR 'Custom Field 'Notes' contains 'Referral''. This fires if the contact came from the website OR their notes mention a referral. This broadens your lead capture.

Test Complex Triggers Thoroughly — After setting up advanced triggers, create test contacts that match and don't match your conditions. Observe if the workflow fires as expected, checking both the 'is' and 'contains' logic. Refine as needed.

✅ Complex triggers require rigorous testing. A single misplaced 'AND' or 'OR' can drastically alter your automation's behavior.

🔥 Pro Tip

For very complex trigger logic, consider breaking it down into multiple simpler workflows chained together with 'Add to Workflow' actions. This makes troubleshooting easier.

Troubleshooting Common Issues

⚠️ My workflow is not firing, even when conditions seem met.

Check for case sensitivity in your 'exact match' or 'contains' phrases. Ensure the workflow is Published, and verify that the trigger type (e.g., 'Contact Tag') correctly corresponds to the event occurring. Also, confirm there are no conflicting or overly restrictive 'AND' conditions.

⚠️ My workflow is firing too often or for the wrong contacts.

Review your 'contains' conditions. A phrase like 'new' might be too broad and appear in many unrelated fields. Refine your phrase, add more specific 'AND' conditions, or consider switching to an 'exact match' ('is') if appropriate.

⚠️ A custom field trigger isn't working as expected.

Ensure the custom field value is actually being updated or set in a way that the trigger can detect. Check if the field type (text, dropdown) aligns with how you're using 'is' or 'contains'. Verify the field name in the trigger matches the actual field name.

⚠️ The workflow fires, but the contact doesn't have the expected data.

This often happens if the trigger fires *before* all relevant contact data is fully saved or updated. Consider adding a small delay (e.g., 1 minute) at the start of your workflow. Also, ensure the data source (form, import) is correctly populating the fields your trigger relies on.

⚠️ Multiple triggers are firing for the same event, causing duplicate actions.

Examine if you have overlapping triggers with similar conditions. Use more specific filters or 'AND' conditions to differentiate them. Ensure you've toggled off 'Allow re-entry' if you only want contacts to go through the workflow once.

Common Mistakes to Avoid

→Confusing 'is' (exact match) with 'contains' (partial match) operators, leading to incorrect trigger activation.
→Ignoring case sensitivity in trigger conditions, causing workflows to miss intended contacts (e.g., 'lead' vs. 'Lead').
→Not thoroughly testing triggers with both matching and non-matching test data before activating the workflow.
→Using overly broad 'contains' phrases that accidentally trigger workflows for irrelevant contacts.
→Forgetting to publish the workflow after making changes to the trigger, leaving the automation inactive.

Frequently Asked Questions

QWhat is the main difference between the 'is' and 'contains' operators in GoHighLevel workflow triggers?

The 'is' operator requires an exact match; the field's value must be identical to the specified text. For example, 'Tag is VIP' only fires if the tag is precisely 'VIP'. The 'contains' operator, conversely, fires if the specified text appears anywhere within the field's value. For instance, 'Notes contains follow-up' fires if the notes field includes 'needs follow-up' or 'initial follow-up call'. 'Is' is for precision, 'contains' is for flexibility.

QCan I use both 'exact match' and 'contains' conditions within a single workflow trigger?

Yes, absolutely. GoHighLevel allows you to add multiple filters to a single workflow trigger. You can combine 'is' and 'contains' operators using 'AND' or 'OR' logic to create highly specific automation conditions. For example, 'Contact Tag is 'Hot Lead'' AND 'Custom Field 'Product Interest' contains 'Software'' would be a valid and powerful combination.

QDoes case sensitivity matter for text-based workflow triggers in GoHighLevel?

Yes, GoHighLevel workflow triggers are generally case-sensitive for text comparisons, especially with the 'is' and 'contains' operators. This means 'new lead' is treated as different from 'New Lead'. Always match the exact casing of your data (tags, custom field values) when setting up your trigger conditions to ensure accuracy and prevent missed automations.

QWhat is the best way to test my workflow triggers to ensure they work correctly?

The best way to test is by creating a test contact and manually triggering the conditions you've set up. For example, add the specific tag, update the custom field, or submit the form that your trigger monitors. Then, check the workflow's 'Execution Log' to see if it fired and if the contact entered the workflow as expected. Adjust your trigger logic if it doesn't behave as intended.

QWhat are some common trigger types where 'exact match' and 'contains phrase' are most useful?

These conditions are highly versatile. 'Exact match' ('is') is excellent for triggers like 'Contact Tag', 'Custom Field Updated' (for dropdown/radio values), 'Form Submitted' (for specific form names), or 'Appointment Status'. 'Contains phrase' is particularly useful for 'Custom Field Updated' (for text fields), 'Notes Added', 'Email Events' (for subject lines), or 'Form Submitted' (for text input fields within the form).

Try GoHighLevel Free

Start your 30-day GoHighLevel free trial

Everything in this guide is in your free trial. 30 days, no credit card — the platform behind 78+ revenue systems.

Start 30-Day Free Trial →

Some links are affiliate links — if you sign up we may earn a commission, at no extra cost to you. We only recommend GoHighLevel because we build on it every day.

Arsalan Zaffar

Revset Labs · Revenue Systems · 78+ GHL Builds

Arsalan writes GHL guides from real build experience — 78+ systems, $9.2M in client pipeline. Wharton, CXL & Google certified.

Connect on LinkedIn

Tags:GoHighLevelWorkflowsAutomationTriggersExact MatchContains Phrase