Salesforce filters

Give your team a reusable way to find records using Salesforce data, such as accounts in a target segment or contacts and leads associated with a campaign. Reps use the filters in Find accounts, Find contacts, and Signals without rebuilding the Salesforce criteria.

As an organization administrator, open Org settings → Salesforce filters. Your organization needs a working Salesforce connection and access to the objects and fields you want to query. For help connecting Salesforce, see Connect any platform.

Each filter is a block with a label, source, and conditions. Decide which values you will fix for everyone and which values reps should choose. These filters narrow search results; field sets separately control fields displayed on records, and CRM sync mappings control supported sync behavior.

1. Select New or Add your first block, then replace Untitled block with a label your team will recognize.
2. Keep Query mode → Single query. Under Source, choose the Salesforce object and Return field. For an account filter querying Account records, return Id; a query on related records needs the field that identifies the account, contact, or lead you want to match.
3. Review Where it appears. Auto derives the placement from the returned records. Override it only when a custom lookup prevents Auto from identifying the intended context.
4. Under Conditions, use Add to add a Condition or an ALL, ANY, or NONE group. Choose the Salesforce field, input type, and operator for each condition.
5. Choose Filled by → You to enter a fixed value, or Rep to let the person using the filter choose. Use Edit condition details to set the Label shown to reps and the available options.

For example, a target-segment filter can return Account IDs, fix a required account category, and let reps choose a territory. Review Rep preview to check that the choices make sense to someone using the search.

A hidden condition has a fixed value and still applies without being shown to reps. Disable turns off the whole block: it disappears from reps' filters and stops applying. Save either change with the rest of the page.

Use a dropdown when reps should choose from a known set instead of entering free text.

1. Choose a suitable type, such as Dropdown or Searchable dropdown, and open Edit condition details.
2. In Choices come from, select A list I type in or an existing Value set.
3. For a typed list, use Add option. Check both Label (shown to user) and Value (sent to Salesforce); a friendly campaign name may need a Salesforce record ID as its value.
4. When available for the selected Salesforce field, Sync from Salesforce replaces the option list with that field's active picklist values. Review the replacement before saving.
5. If you choose a value set, review the example choices and keep suitable Fallback options. Use Open this value set to inspect the source.

A value set supplies choices from a reusable rule over live data, such as currently active campaigns. A typed list is a list you maintain in this editor. Shared inputs in a multi-query filter can also use value sets; they are not tied to one Salesforce field, so their options cannot use Sync from Salesforce.

1. Select Create a value set in the dropdown options editor. It opens the value-set editor in a new tab.
2. Describe the choices you need in Chat, including the source, matching criteria, the label reps should see, and the value Salesforce expects. For example, ask for the IDs and names of campaigns with the status your team uses for current campaigns.
3. Review the proposed rule and its approval request before approving creation. Open the resulting value set's Values tab to check what it produces.
4. Review Values, Last refreshed, and Last run. Use Filter values to find a particular choice. If you have organization admin or configuration management access, select Refresh now when you need a new run.
5. Return to Salesforce filters, choose the new set in Choices come from, then test and save the filter.

A new or edited set may not have produced values yet. Until usable values are available, filters keep their typed fallback options. Refresh now starts a refresh; it does not mean new values are ready immediately. Check Last refreshed and Last run afterward. Previously resolved values remain available while a refresh is running, and a failed update can leave the last successful values in use.

The Values tab reports failed runs, capped results, or values that cannot be used in filters. Correct the rule in the value set's Chat and review the resulting change before relying on the new choices.

Use Multiple queries (advanced) when one filter needs to combine separate Salesforce queries. For example, campaign membership may identify contacts through one return field and leads through another, while reps choose the campaign only once.

1. Change Query mode to Multiple queries (advanced). Converting an existing single query keeps it as the first query and turns its rep-supplied values into shared inputs.
2. Under Shared inputs, select Add input. Give it a Label shown to reps, choose its Input type, and configure its options, including a value set when useful.
3. Use Add query for each source. Choose its Salesforce object, Return field, and conditions.
4. In each query, connect the appropriate conditions to the shared inputs through Value source. Every shared input must be used in every query. Add fixed conditions where the source needs its own restrictions.
5. Review the combined filter using Test selections, Test, and Rep preview, then save the page.

The filter includes matches from any of its queries and includes duplicate IDs once. Other selected filters still narrow those results. This combines query results; it does not require a record to match every query.

To return to Single query, leave one query and use each shared input exactly once in it. If the switch is unavailable, follow its explanation before removing anything.

1. Check Rep preview to see the inputs your team will get. Confirm the labels, choices, placement, and any conditions that apply silently.
2. Inspect Compiled SOQL and select Test to query Salesforce. For multiple queries, set representative Test selections first; blank shared inputs are omitted from each test query.
3. Review the match count and any error. Multiple queries show combined unique IDs and individual query counts. A count ending in + is capped rather than an exact total. Change the selections and test again if the result is unexpected.
4. Resolve the editor's validation messages, then select Save changes. Wait for Salesforce filter settings saved. Testing alone does not save the configuration.
5. Open Find accounts, Find contacts, or Signals as appropriate. Find the block in the corresponding Account or Contact section of Add filter, choose its values, and inspect matching records.

Save a useful combination as a saved view so the team can return to it. Saving the filter configuration makes the reusable block available; it does not create a prospect list or change Salesforce records.

• Cannot save: read the block's validation messages. Check the source and return field, matching field and input types, operators, required values, and shared-input references. All blocks on the page must be valid.
• Salesforce test fails: read the returned error and check the connection, object and field API names, permissions, and expected value types. A field label and its API name may differ.
• Block is missing for reps: confirm it is enabled, saved, and placed in the intended Account or Contact context. Hidden individual conditions are not shown, even though they still apply.
• Dropdown choices look old: open the value set's Values tab and check Last refreshed and Last run. A refresh may still be running or a failed run may leave earlier values in use.
• Value set is missing, unresolved, or empty: check the warning and the typed fallback options. Choose another set or correct its rule; do not assume an empty set will remove all choices from the filter.
• Too many or too few matches: check hidden fixed conditions, the selected values, the return field, and other active filters. Multiple queries combine matches from any query. Use representative test selections to isolate the difference.

For help, contact support with the filter label, the affected search, the test error or result, and one example of the record you expected to match.