HubSpot Process Documentation

Metadata

• Generated by: HubSpot Documentation Engine
• Total process candidates: 1
• Workflow assessment scope: name_contains via DOCS_WORKFLOW_PREFIXES: ELEVATE, Quality (86/500)
• List assessment scope: name_contains via DOCS_LIST_PREFIXES: ELEVATE (45/2191)
• Status: draft

ELEVATE - Clear n4f_no_activity_after_assignment if activity happens

METADATA title: ELEVATE - Clear n4f_no_activity_after_assignment if activity happens type: process domain: ELEVATE objects: [Lead] status: draft

User Story (optional)

Logic not derivable from system.

Why

• Why this process exists: Logic not derivable from system.
• What business problem it solves: Logic not derivable from system.
• What breaks if removed: HubSpot would stop executing the system behavior listed below; business impact is not derivable from system alone.

How It Works

Trigger

• Exact trigger from workflow: HubSpot enrollment criteria type: EVENT_BASED
• Criteria type: EVENT_BASED
• Filter-like criteria returned: 5
• Property references: hs_name, hs_value
• List references: none detected
• Filter types: PROPERTY: 2
• Operators: ALL_PROPERTY: 1, HAS_COMPLETED: 1, IS_EQUAL_TO: 1, IS_KNOWN: 1, STRING: 1
• Trigger logic:
  • Enrollment criteria type: EVENT_BASED
  • Enrollment branch 1:
    • AND group
      • hs_name equals hs_last_activity_date
      • hs_value is known

Steps

Step 1 - Action 1

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: Workflow start action returned by HubSpot
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Last Activity Date (hs_last_activity_date), Owner assigned date (hubspot_owner_assigneddate); lists: none detected

DATA MEANING:

• Last Activity Date (hs_last_activity_date): The date of the last activity. Defaults to the date of the primary associated contact. If not present, looks to the date of the primary associated company.
• Owner assigned date (hubspot_owner_assigneddate): The most recent timestamp of when an owner was assigned to this record. This value is set automatically by HubSpot.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: activity after assignment
  • Condition summary: activity after assignment
  • Default branch: no
  • Next action IDs: 2
  • Referenced properties: Last Activity Date (hs_last_activity_date), Owner assigned date (hubspot_owner_assigneddate)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Last Activity Date is after
• Branch: no activity after assignment
  • Condition summary: no activity after assignment
  • Default branch: yes
  • Next action IDs: workflow exit or not returned
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: no activity after assignment

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 2 - Action 2

• What happens: Sets HubSpot property values; properties: n4f_no_activity_after_assignment = static value No
• What triggers it: After action 1
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: n4f_no_activity_after_assignment; lists: none detected

DATA MEANING:

• n4f_no_activity_after_assignment: Used to detect if after assignment of a lead, the lead owner did an activity. Used in negative reports to identify stalling leads.

ACTION EVIDENCE:

• Action category: set_property
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: property_name, value
• property_name: n4f_no_activity_after_assignment
• value: static value No

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• n4f_no_activity_after_assignment is set or updated; value: static value No; confidence: high. Purpose: Used to detect if after assignment of a lead, the lead owner did an activity. Used in negative reports to identify stalling leads.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

System Behavior

• Workflow actions: 2
• Branch actions: 1
• Custom code actions: 0
• Property operations: 1
• List dependencies: 0
• Action categories: list_branch: 1, set_property: 1
• Property operation types: set_property: 1
• Associations created: listed under Outcomes when custom code exposes association evidence.

Outcomes

• Objects created: Logic not derivable from system.
• Objects updated: Lead: 1 property operation(s)
• Associations created: Logic not derivable from system.
• Marketing emails sent: 0
• Internal notifications: 0
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 0

How It Is Implemented

Workflows

• Workflow: ELEVATE - Clear n4f_no_activity_after_assignment if activity happens
  • Workflow ID: 3151114461
  • Revision ID: 9
  • Enabled: yes
  • Current HubSpot description: Updates n4f_no_activity_after_assignment to “No” when there is no activity recorded after the owner is assigned, triggered by changes to the last activity date property.
  • Purpose: Updates n4f_no_activity_after_assignment to “No” when there is no activity recorded after the owner is assigned, triggered by changes to the last activity date property.
  • Key logic: list_branch: 1, set_property: 1
  • Branching logic: 2 branch detail(s) returned by HubSpot
  • activity after assignment: activity after assignment; next actions: 2; properties: hs_last_activity_date, hubspot_owner_assigneddate; lists: none detected
  • no activity after assignment: no activity after assignment; next actions: not returned; properties: none detected; lists: none detected
  • Dependencies: lists: none detected; properties: Last Activity Date (hs_last_activity_date), hs_name, hs_value, Owner assigned date (hubspot_owner_assigneddate), n4f_no_activity_after_assignment; custom code: none detected

Property Context

• Last Activity Date (hs_last_activity_date) - The date of the last activity. Defaults to the date of the primary associated contact. If not present, looks to the date of the primary associated company. Roles: branch condition, step data. internal name: hs_last_activity_date; object: Leads; type: datetime.
• hs_name - No HubSpot property description returned. Roles: trigger condition. internal name: hs_name; object: object not returned; type: not returned.
• hs_value - No HubSpot property description returned. Roles: trigger condition. internal name: hs_value; object: object not returned; type: not returned.
• Owner assigned date (hubspot_owner_assigneddate) - The most recent timestamp of when an owner was assigned to this record. This value is set automatically by HubSpot. Roles: branch condition, step data. internal name: hubspot_owner_assigneddate; object: Line Items; type: datetime.
• n4f_no_activity_after_assignment - Used to detect if after assignment of a lead, the lead owner did an activity. Used in negative reports to identify stalling leads. Roles: property updated, step data. internal name: n4f_no_activity_after_assignment; object: Leads; type: enumeration.

Evidence And Gaps

• Domain evidence: Derived from configured workflow scope prefix: ELEVATE
• Quality flags: branching_logic_present: Workflow contains branching logic. property_operations_detected: Workflow appears to write or copy one or more properties.
• Narrative context: not used as source of truth.