Documentation Index

Fetch the complete documentation index at: https://support.6sense.com/llms.txt

Use this file to discover all available pages before exploring further.

Workflow Nodes Priority Profile Filter

Prev Next

The priority profile filter lets workflow designers branch logic or target outreach specifically to high-quality contacts whose information has been verified by 6sense.

“Verified” means that the contact’s name, role, and email have been validated by 6sense, and the validation is refreshed at least once every 60 days. These are contacts who are likely to be decision-makers at their company, and therefore are higher-quality targets for outbound sales and marketing outreach.

Audience and Data Workflows support a priority profile filter for the following nodes:

  • Decision node: Affects which decision node branch the results follow.

  • Purchase Contacts node: Controls which contacts are in the set of contacts to be purchased.

Prerequisites and considerations

  • Priority profile is a contact-related filter that returns the accounts of the relevant contacts.

  • Priority profile data is populated by the 6sense daily data pipeline.

    • If there are no priority profile contact records for the account, you won’t see any in a workflow run where Priority Profile = True.

  • Priority profile does not require the Predictive add-on (despite its placement in the 6sense AI section of the filters list).

Access the priority profile filter

To access the priority profile filter from a decision or Purchase Contacts node:

  1. Select the node’s Edit button.

  2. Select Edit Condition.

  3. From the filters list go to 6Sense AI > Contact and select Priority Profile.

Priority profile filter properties

The priority profile filter asks whether or not a contact is considered as verified, either:

  • True: Output only includes accounts who have contacts who are verified as Priority Profiles.
    OR

  • False: Output only includes accounts who have contacts who are not verified as Priority Profiles.

Document changelog

Aug 12 2026: First release