OA
OpsAgent

Anonymize Number

Last updated 3 weeks ago

The Anonymize Number workflow action protects sensitive numeric data by randomizing, rounding, zeroing, or masking values. Use it to obscure exact figures like revenue amounts, scores, or identifiers while keeping data useful for segmentation and reporting.

How It Works

Add the Anonymize Number action to any contact, company, deal, or ticket workflow in HubSpot. When a record reaches this step, the app reads a number from the CRM property you selected, applies your chosen anonymization method, and returns the anonymized value so your workflow can store or act on it.

Action Inputs

When you add this action to your workflow, you'll configure the following fields:

Field Required Description
Number to Anonymize Yes Pick a CRM number property from the enrolled record. This is the numeric value that will be anonymized.
Anonymization Type No Choose how the number should be anonymized. Options: Randomize Range -- adjusts the number up or down by a random percentage; Round to Nearest -- rounds the number to the nearest value you specify; Zero Out -- replaces the number with zero; Mask Digits -- replaces all digits with zeros.
Range Percentage No When using the Randomize Range method, enter the maximum percentage the number can vary in either direction. Defaults to 10 if left blank.
Round To No When using the Round to Nearest method, choose the rounding target. Options: 10, 100, 1000, 10000.

Action Outputs

After the action runs, the following values are available for use in later workflow actions (e.g., copy to property, branching):

Output Type Description
Anonymized Number Number The numeric value after anonymization has been applied
Success Yes/No Whether the anonymization completed without errors
Error Message Text If something went wrong, this contains a description of the problem

Tip: To learn how to use these output values in later workflow actions (e.g., copy to a property, use in branching logic), see Using workflow action outputs in the HubSpot Knowledge Base.

Usage Examples

Protecting Deal Amounts for Shared HubSpot Reports

When sharing reports with external partners or broader teams, you may need to obscure exact deal values while preserving general magnitude for trend analysis.

  1. Trigger a deal-based workflow when a deal moves to Closed Won
  2. Add the Anonymize Number action and select the Deal Amount property
  3. Set the Anonymization Type to Randomize Range and the Range Percentage to 10
  4. Copy the Anonymized Number to a custom property like "Anonymized Amount" for use in shared dashboards

Rounding Contact Scores for Privacy in HubSpot

Exact HubSpot scores can reveal too much about individual engagement patterns. Rounding scores to broader buckets gives you useful segments without exposing precise activity data.

  1. Trigger a contact-based workflow when the HubSpot Score property is updated
  2. Add the Anonymize Number action and select the HubSpot Score property
  3. Set the Anonymization Type to Round to Nearest and Round To to 10
  4. Store the Anonymized Number in a custom property and use it for list segmentation

Zeroing Out Sensitive Identifiers in HubSpot

When a contact requests data deletion under privacy regulations, you may need to erase numeric identifiers stored in custom properties without deleting the entire record.

  1. Trigger a contact-based workflow when a contact submits a data deletion request form
  2. Add the Anonymize Number action and select the custom number property containing the identifier
  3. Set the Anonymization Type to Zero Out
  4. Copy the Anonymized Number (zero) back to the original property, effectively erasing the value

Tips

  • Randomize Range preserves relative scale. A 50,000 deal with a 10% range becomes something between 45,000 and 55,000, keeping the number realistic for reports while hiding the exact figure.
  • Rounding is ideal for bucketed reporting. Rounding to the nearest 1,000 turns values like 12,345 into 12,000, which is often enough precision for dashboards and trend analysis.
  • Zero Out is permanent. Once a value is replaced with zero, it cannot be recovered. Use this method when you need to fully erase a numeric value.
  • Combine methods for stronger anonymization. You can chain multiple Anonymize Number actions in a workflow -- for example, first randomize by 10%, then round to the nearest 100.