Check whether a field is empty in workflow conditions
Updated
Who can do this: Super Admins, Creators, Collaborators and Integrators can publish the workflow
Most workflow conditions compare a field to a value, such as an amount greater than 50,000. The is empty and is not empty operators check something else: whether a field on the CRM record has a value at all. Use them to send records with a missing value down a different branch from records where it's filled in.
Where you can use them
The operators appear in the condition builder on these parts of a workflow:
The CRM trigger
The project owner card
The playbook card
The conditional modules card
Customer user conditions, for Salesforce and HubSpot
HubSpot account association conditions
On the CRM trigger, every field type's operator list includes is empty and is not empty, except on some Salesforce triggers (see Salesforce triggers without the updated trigger connection). On the conditional modules, customer user and HubSpot account association conditions, string, number, boolean, date and object fields offer the full operator list, including is empty and is not empty. There, custom-type fields offer only is equal to, is empty and is not empty.
What counts as empty
is empty matches when the field has no value on the triggering record.
is not empty matches when the field has any value.
A field counts as empty when it has no value, holds text that's blank or only spaces, or is an empty list. A 0 or a false counts as a value, so it matches is not empty.
Add an empty check
Open the workflow. If it isn't already in editing, select Edit from v followed by the version number, such as Edit from v3. This needs permission to edit workflows.
Go to the card you want to add a condition to.
On the project owner, playbook or conditional modules card, select Add Condition to add a new branch. The trigger and customer user conditions don't have this button, so skip this step there.
Inside the branch, select Condition to add a row. HubSpot account association conditions don't have this button, so there you change the operator on an existing row instead.
Choose the field to check, such as a close date or a custom CRM field.
From the operator list, choose is empty or is not empty. The value input disappears, because there's nothing to compare against.
Optional: To add more rows to the branch, select Condition again. On the project owner and playbook cards, once a branch has more than one row, choose whether the record must match All or Any of them. On the CRM trigger, choose All, Any or Custom. On the conditional modules, customer user and HubSpot account association conditions, every row must match.
Select Save, then select Publish.
Condition changes don't save on their own. Publish stays turned off while the workflow has unsaved changes, so select Save first. The condition summary reads like Close Date is not empty. If you don't have permission to publish workflows, the Publish button is turned off.
To check how a record is routed before you publish, see Test a workflow with Debug. To combine conditions with your own AND and OR logic, see Using Custom Logic in Workflow Triggers.
Salesforce triggers without the updated trigger connection
Some Salesforce triggers don't use the updated Salesforce trigger connection. On those triggers, is empty and is not empty aren't in the operator list.
If a rule on one of those triggers already has an empty check, the builder shows this notice:
This rule uses an empty/not-empty check, which needs the updated Salesforce trigger connection. Publishing will be rejected — contact OnRamp support to enable it, or use a different operator.
To publish, contact us to turn on the updated connection, or change the row to a different operator.