Data Workflows Glossary

Prev Next

This page defines terms used in Data Workflows.

Data Workflows general terminology

  • View Performance Details: View records modified by a workflow over a period of time. 

  • Branch: Connecting two nodes. 

  • Canvas: UI to build a workflow by dragging and dropping nodes and connecting these nodes. 

  • Conditions: A set of filters that allows for selection of desired records. Supported by decision nodes, timer nodes, and action nodes.  

  • Create from Scratch: Begins a workflow with only a ‘start’ node.  

  • Decision Node Filter Logic: Value vs Field 

    • Value: filters on the value in a specific field 

    • Field: creates a comparison of the values in the same field between two records 

  • Filters: CRM filters which allow for a selection of desired records meeting certain conditions. Supported by decision nodes and other nodes. 

  • Mapping Profile: Defines which data will enrich a record in CRM and allows a user to determine if this data can overwrite or only fill in if blank.  

  • Node: The building block of a workflow performs desired actions. 

  • Node Config: This refers to the configuration panel for decision nodes and other nodes.  

  • Node Drawer: The toolbar located on the right side of the canvas. This allows the user to select a node to drag onto the canvas.  

  • On-Demand Workflows: Manually execute workflows anytime by clicking Run Now.  

  • Preview: Generate a preview of the workflow so that the user can see what accounts and people will be added to a particular channel.  

  • Real-time Workflows: Executes workflow in 5+ minutes when a record is created. 

  • Run History: View workflow run history for each execution. 

  • Scheduled Workflows: Workflows can be executed at a predefined day and frequency.  

  • segment: A collection of accounts meeting user-defined filter criteria built within the ABM platform 

  • Workflow: A series of nodes connected in such a way as to automate desired tasks efficiently at scale. 

  • Workflow Path: A visual representation of the steps taken for a particular action to have occurred.  

  • Workflow Status:  

    • Draft: The workflow is saved as a draft but has not been published. The workflow will not run in this state. If there is an existing published version of the workflow, that version will continue to run. 

    • Published: The workflow is running at the configured schedule. It will continue to run until it is unpublished. 

    • Unpublished: The workflow will no longer run at the configured schedule. 

    • Published + Draft: Draft changes are being added to a published, running workflow.  

    • Edit: Edit the existing version of a play. 

    • View Published Version: View existing play as read-only. 

Data Workflows node terminology

  • Decision Nodes:  

    • Custom T/F: Provides a simple format for setting up classic boolean (yes/no) conditions within your flow. Custom T/F Decision nodes define conditions that narrow records based on the Workflow’s overall intention or theme (such as including or excluding records based on the value in a CRM field). 

    • Custom Branching: Allows you to create multiple branches based on values in CRM filters. 

  • Enrich Nodes

    • Accounts: Export Firmographic and people-level data to CRM records defined by custom mapping profiles. Mapping profiles are set at the global level, but can be customized at the node level to provide flexibility based on use case.  

    • Contacts: Export account firmographic and people-level data to CRM records defined by custom mapping profiles. Mapping profiles are set at the global level, but can be customized at the node level to provide flexibility based on use case. 

    • Leads: Export account firmographic and people-level data to CRM records defined by custom mapping profiles. Mapping profiles are set at the global level, but can be customized at the node level to provide flexibility based on use case. 

  • Create Accounts: Creates net new accounts in CRM. 

  • Purchase Contacts: Configure people-level filters to purchase the right contacts for your programs. Common filters should include 6sense persona or title filters. 

    • Save purchased contacts to CRM. 

      • Save as Leads (Salesforce) or Contacts (HubSpot). 

      • Save as Contacts (Salesforce or HubSpot). 

    • Save purchased contacts to CSV 

  • Push Segment Names: Provides the ability to push the name of a segment into a comma delineated field on the account, contact, or lead object within CRM.  

  • Export Scores: Allows customers who have predictive models to push 6sense predictive scores into CRM. Scores included: 

    • Account Score Data Available to Push to CRM

      • Account Buying Stage  

      • Account Intent Score ​ 

      • Account Profile Fit ​ 

      • Account Profile Score ​ 

      • Account Reach Score ​ 

      • Account Scores Last Updated ​ 

    • Contact Score Data Available to Push to CRM

      • Contact Grade   

      • Contact Intent Score   

      • Contact Profile Fit   

      • Contact Profile Score   

      • Contact Account Buying Stage   

      • Contact Account Intent Score   

      • Contact Account Profile Fit   

      • Contact Profile Score   

      • Contact Scores Last Updated   

    • Lead Score Data Available to Push to CRM

      • Lead Grade ​ 

      • Lead Intent Score ​ 

      • Lead Profile Fit ​ 

      • Lead Profile Score ​ 

      • Lead Account Buying Stage ​ 

      • Lead Account Intent Score ​ 

      • Lead Account Profile Fit ​ 

      • Lead Profile Score ​ 

      • Lead Scores Last Updated ​

    • 6QA Data pushed to CRM (Field: Description) 

      • Account 6QA: The 6QA status of the account for the product. 

      • Account 6QA Start Date: The date the account qualified for 6QA status (YYYY-MM-DD). 

      • Account 6QA End Date: The date the account was disqualified from 6QA status (YYYY-MM-DD). 

      • Account 6QA Age in Days: Days the account has been in 6QA status. 

  • Action –> Update: Provides the ability to update a field on an account, contact, or lead object within CRM with custom text defined by the user setting up the workflow.  

    • Update Account: Fields on an account record. 

    • Update Contact: Fields on a contact record. 

    • Update Lead: Fields on a lead record.