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 - Detect and alert overwrites in contact special interest property

METADATA title: ELEVATE - Detect and alert overwrites in contact special interest property type: process domain: ELEVATE objects: [Contact] 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 n4f_special_interest
      • hs_value is known

Steps

Step 1 - Action 8

• 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: 4f_Special interest_Backup (n4f_special_interest_backup); lists: none detected

DATA MEANING:

• 4f_Special interest_Backup (n4f_special_interest_backup): Note: Please only APPEND users This field is used to give users quick access to contacts they would like to monitor/follow.

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: backup unknown
  • Condition summary: backup unknown
  • Default branch: no
  • Next action IDs: 9
  • Referenced properties: 4f_Special interest_Backup (n4f_special_interest_backup)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_Special interest_Backup is unknown
• Branch: backup known
  • Condition summary: backup known
  • Default branch: yes
  • Next action IDs: 2
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: backup known
      • Next action: 2

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: Runs custom code; 3 inputs; 0 outputs
• What triggers it: After action 8
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

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:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: n4f_special_interest, n4f_special_interest_backup, n4f_special_interest_person_alert
• Conditions detected in code: Code condition: if (!token) { Code condition: if (overwriteDetected && userId) { Code condition: if (overwriteDetected) { Code condition: if (removed.length > 0 && isAllowedEditor) {
• CRM/API operations detected: updates records or resources
• Concrete CRM operations: read by ID: contacts; update: contacts
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, filters collections, replaces or cleans text patterns, splits a value into parts
• Outputs returned to workflow: outputFields, overwrite_detected
• HubSpot CRM objects affected or referenced: contacts
• Associations handled: none detected
• Workflow control: contains asynchronous execution, returns output fields to later workflow actions
• Safeguards/error handling: error or warning logging, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 118 lines returned; code body analyzed but omitted from docs

Step 3 - Action 1

• What happens: Sets HubSpot property values; properties: n4f_special_interest_backup = returned value object with keys: appendPropertyName, type
• What triggers it: After action 2
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Special interest_Backup (n4f_special_interest_backup); lists: none detected

DATA MEANING:

• 4f_Special interest_Backup (n4f_special_interest_backup): Note: Please only APPEND users This field is used to give users quick access to contacts they would like to monitor/follow.

ACTION EVIDENCE:

• Action category: set_property
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: property_name, value
• property_name: n4f_special_interest_backup
• value: object with keys: appendPropertyName, type

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:

• 4f_Special interest_Backup (n4f_special_interest_backup) is set or updated; value: returned value object with keys: appendPropertyName, type; confidence: high. Purpose: Note: Please only APPEND users This field is used to give users quick access to contacts they would like to monitor/follow.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 4 - Action 6

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 1
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: 4f_Special interest_person_alert (n4f_special_interest_person_alert); lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

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: alert
  • Condition summary: alert
  • Default branch: no
  • Next action IDs: 5
  • Referenced properties: 4f_Special interest_person_alert (n4f_special_interest_person_alert)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_Special interest_person_alert is known
• Branch: no alert
  • Condition summary: no alert
  • 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 alert

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 5 - Action 5

• What happens: Sends an internal notification
• What triggers it: After action 6
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: Alaaarm, replaced values in 4f_Special interest”
• team_ids: Demand-Gen & CRM

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:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 6 - Action 7

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 5
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

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:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 7 - Action 4

• What happens: Sets HubSpot property values; properties: n4f_special_interest_person_alert = static value not returned
• What triggers it: After action 7
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Special interest_person_alert (n4f_special_interest_person_alert); lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

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_special_interest_person_alert
• value: static value not returned

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:

• 4f_Special interest_person_alert (n4f_special_interest_person_alert) is set or updated; value: static value not returned; confidence: high.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 8 - Action 9

• What happens: Sets HubSpot property values; properties: n4f_special_interest_backup = value from property n4f_special_interest
• What triggers it: After action 8
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Special interest_Backup (n4f_special_interest_backup); lists: none detected

DATA MEANING:

• 4f_Special interest_Backup (n4f_special_interest_backup): Note: Please only APPEND users This field is used to give users quick access to contacts they would like to monitor/follow.

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_special_interest_backup
• value: value from property n4f_special_interest

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:

• 4f_Special interest_Backup (n4f_special_interest_backup) is set or updated; value: value from property n4f_special_interest; confidence: high. Purpose: Note: Please only APPEND users This field is used to give users quick access to contacts they would like to monitor/follow.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

System Behavior

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

Outcomes

• Objects created: Logic not derivable from system.
• Objects updated: Contact: 3 property operation(s), contacts (custom code contains update call)
• Associations created: Logic not derivable from system.
• Marketing emails sent: 0
• Internal notifications: 1
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 1

How It Is Implemented

Workflows

• Workflow: ELEVATE - Detect and alert overwrites in contact special interest property
  • Workflow ID: 2426462437
  • Revision ID: 32
  • Enabled: yes
  • Current HubSpot description: Detects changes removing values from a contact’s special interest property, backs up the original values, alerts the responsible user, and sends a notification if an overwrite occurs.
  • Purpose: Detects changes removing values from a contact’s special interest property, backs up the original values, alerts the responsible user, and sends a notification if an overwrite occurs.
  • Key logic: connected_action: 1, custom_code: 1, internal_notification: 1, list_branch: 2, set_property: 3
  • Branching logic: 4 branch detail(s) returned by HubSpot
  • alert : alert ; next actions: 5; properties: n4f_special_interest_person_alert; lists: none detected
  • no alert: no alert; next actions: not returned; properties: none detected; lists: none detected
  • backup unknown: backup unknown; next actions: 9; properties: n4f_special_interest_backup; lists: none detected
  • backup known: backup known; next actions: 2; properties: none detected; lists: none detected
  • Dependencies: lists: none detected; properties: hs_name, hs_value, 4f_Special interest (n4f_special_interest), 4f_Special interest_Backup (n4f_special_interest_backup), 4f_Special interest_person_alert (n4f_special_interest_person_alert); custom code: 1 custom code action(s)

Property Context

• 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.
• 4f_Special interest (n4f_special_interest) - This field is used to give users quick access to contacts they would like to monitor/follow. It is a multi-user field as at 4flow we do not follow the concept of “ownership” of contacts. Contact owner is not actively maintained, but 4flowers are asked to append their names to this field. Roles: reference. internal name: n4f_special_interest; object: Contacts; type: enumeration.
• 4f_Special interest_Backup (n4f_special_interest_backup) - Note: Please only APPEND users This field is used to give users quick access to contacts they would like to monitor/follow. Roles: branch condition, property updated, step data. internal name: n4f_special_interest_backup; object: Contacts; type: enumeration.
• 4f_Special interest_person_alert (n4f_special_interest_person_alert) - No HubSpot property description returned. Roles: branch condition, property updated, step data. internal name: n4f_special_interest_person_alert; object: Contacts; type: string.

Evidence And Gaps

• Domain evidence: Derived from configured workflow scope prefix: ELEVATE
• Quality flags: custom_code_present: Workflow appears to contain one or more custom code actions. 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.