App guide

Property History Workflow Actions guide

Use previous, original, and historical property values directly in HubSpot workflows.

MarketplaceInstall appPricing

Capabilities

Key features

01Get Previous Property Value
02Get Original Property Value
03Count Property Changes
04Contacts, Companies, Deals and Tickets
05Read-only CRM access; history values are not stored by Plugivo

Implementation

Setup guide

1

Connect your HubSpot account

Install Property History Workflow Actions and approve read access to Contacts, Companies, Deals and Tickets. Open the app settings in HubSpot to check the connection and execution allowance. The trial includes 100 lifetime executions per account, without a time limit or credit card.

Property History app settings showing 5 of 100 trial executions used and 95 runs remaining.
Click to enlarge
App settings show execution usage and remaining trial runs. This demo account has used 5 of its 100 executions.
2

Add an action and choose a property

Open a Contact, Company, Deal or Ticket workflow. Choose Get Previous Property Value, Get Original Property Value, or Count Property Changes, then search the property selector for a readable property. The workflow supplies the enrolled record; no record ID or tracking mapping is required.

Three steps: choose a record property, read previous or original values or count changes, then branch, save or notify with workflow outputs.
Click to enlarge
Choose a property, read its available HubSpot history, and use the result in later workflow actions.
3

Example: get the previous Job Title

In a Contact workflow, add Get Previous Property Value and choose Job Title. Enroll a test contact with known history. The example returns Marketing Associate as the previous value while the current value is Marketing Manager, with a UTC timestamp for the previous version.

Contact workflow with manual enrollment, Get Previous Property Value for Job Title, and Create task.
Click to enlarge
Contact workflow using Get Previous Property Value for Job Title, followed by a native Create task action.
Successful previous Job Title output showing Marketing Manager as current value and Marketing Associate as previous value.
Click to enlarge
Successful result: current value Marketing Manager; previous value Marketing Associate; three recorded history versions.
4

Example: get the original Deal Amount

In a Deal workflow, add Get Original Property Value and choose Amount. This example returns an original value of 1000 and a current value of 5000. Original means the oldest recorded value available from HubSpot; it is not guaranteed to be the value at record creation.

Deal workflow with manual enrollment and Get Original Property Value configured for Amount.
Click to enlarge
Deal workflow using Get Original Property Value for Amount.
Successful original Deal Amount output showing original value 1000 and current value 5000.
Click to enlarge
Successful result: original Amount 1000; current Amount 5000; three recorded history versions.
5

Example: count Ticket status changes

In a Ticket workflow, add Count Property Changes and choose Ticket status. This example has four recorded versions and three changes. Change count counts unequal adjacent values across the available history, while History version count counts the recorded versions themselves.

Ticket workflow with manual enrollment and Count Property Changes configured for Ticket status.
Click to enlarge
Ticket workflow using Count Property Changes for Ticket status.
Successful Ticket status history output showing three changes, four recorded versions, and first and latest timestamps.
Click to enlarge
Successful result: change_count is 3 and history_version_count is 4, with first and latest recorded timestamps.
6

Check Success before saving a value

Add a branch on Success or Status before using a history value. In the Yes branch, use HubSpot's Edit record action to save the Previous Value output to a separate Previous Job Title property. The history action only reads data; HubSpot performs the update. NO_DATA means no history or no previous version is available. ERROR includes an error code and execution ID.

Contact workflow branching on Success and setting Previous Job Title from the Previous Value output in the Yes branch.
Click to enlarge
Branch on Success, then use Edit record to save the Previous Value output on the contact.
Sample contact properties showing Job title Marketing Manager and saved Previous Job Title Marketing Associate.
Click to enlarge
The sample contact keeps Job title as Marketing Manager and stores Marketing Associate in Previous Job Title.
7

Branch on Change Count to notify your team

After checking the result, branch on Change Count. The example routes tickets with a count of at least 2 to an internal notification. This count covers all available history, rather than only changes during a time window or since the last enrollment.

Ticket workflow using Count Property Changes and a branch where Change Count is greater than or equal to 2.
Click to enlarge
Use the Change Count output in a native branch; choose a notification action for the matching path.
8

Test before broad enrollment

Compare each output with the history of a test record in HubSpot. Check the no-data path as well as successful values, including blanks and repeated versions. Use a separate destination property when saving a historical value so the current source property stays useful. Return to app settings to check usage before enrolling more records.

Reference

Frequently asked questions

Is the original value the record creation value?
It is the oldest recorded value available through the HubSpot API. HubSpot may have incomplete or migrated history; the app cannot guarantee a value from record creation.
Which value formats are returned?
Values use the HubSpot API string format, including numeric strings, date strings, internal dropdown or deal-stage values, owner IDs, boolean strings and semicolon-separated checkbox values. Timestamps use UTC ISO 8601 strings.
How are blanks and repeated versions handled?
Blank and repeated recorded versions are preserved. Previous means the immediately preceding version, even if blank or identical. Change count counts unequal adjacent values. Conflicting values at the same timestamp return an error because their sequence is ambiguous.
What consumes the allowance?
One authenticated action invocation with valid inputs uses one execution, including no-data results and failed HubSpot lookups. Retrying the same execution does not use another unit. Property-selector requests are free. Paid allowance renews each calendar month in UTC; the trial is 100 total executions and survives reinstalling.
Does Plugivo store CRM history?
No. Property values are fetched, used for the workflow result, and discarded. Operational usage records contain only the action, property name, object type and enrolled record ID.
What happens at the limit?
The action returns USAGE_LIMIT_REACHED and performs no history lookup. There are no automatic overages. Change plans in the Plugivo portal to continue.

Ready to put the app to work?

Install Property History Workflow Actions and add the action to your HubSpot workflow. No credit card required for the trial.

Install Property History Workflow Actions
App guide