PrevVal Documentation

Your comprehensive guide to capturing and tracking previous values in HubSpot

From installation to advanced usage, we've got you covered with detailed guides and examples to help you make the most of PrevVal.

Install PrevVal Back to PrevVal Manage Subscription

Quick Navigation

Quick Start

Get up and running with PrevVal in minutes. Follow our simple installation guide.

Documentation

Detailed guides and examples for making the most of PrevVal.

Support

Need help? Our support team is here to assist you every step of the way.

Installation & Setup

Follow our step-by-step process to start capturing previous values in HubSpot.

1. Prerequisites

  • • Active HubSpot account
  • • Admin access to HubSpot
  • • Your HubSpot Portal ID
  • • Active PrevVal subscription

2. Installation

Click Install. You'll be redirected to the install page, where you can read some help text about having a Subscription first. Then, click install again, and it will redirect you to the HubSpot OAuth page to connect the app.

3. Confirmation

Once authorized, you'll receive a success message. Then you're ready to start tracking previous values!

Detailed Installation Steps

Step 1: Verify Requirements

  • Confirm you have Admin access to your HubSpot portal
  • Locate your HubSpot Portal ID (found in Account Settings)
  • Make sure you have an active PrevVal subscription
  • Check that your HubSpot plan includes Workflows

Step 2: Installation Process

  1. Click the "Install PrevVal" button
  2. You'll be redirected to the Install Page
  3. Review the page prior to clicking "Install Now"
  4. Review and accept the permissions request in HubSpot
  5. Wait for the success confirmation

Step 3: Verify Installation

After installation, you should:

  • See PrevVal actions available in your workflows
  • Be able to access the PrevVal dashboard *Coming Soon*
How to Configure PrevVal in Workflows

Setting up PrevVal is simple - just add it to any HubSpot Workflow Objects (Contact, Companies, Deals, Tickets, & Leads) and specify which properties you want to track.

1

Add PrevVal Action

In your HubSpot workflow, click "+" to add an action, then select "Set Previous Property Value" from the PrevVal app integrations.

2

Configure "Get" Property

Enter the internal property name you want to track in the "InternalPropertyToGet" field. For example, use "amount" for Deal Amount.

3

Set "Update" Property

Enter the internal property name where you want to store the previous value in the "InternalPropertyToUpdate" field. For example, use "previous_amount" for Previous Amount.

4

Optional Batch Processing

Check "Is Batch Request" if you want to process multiple records at once. This is useful for bulk operations or when updating many records simultaneously.

See PrevVal in Action

Watch how to configure PrevVal
Back to workflows
File Edit Settings View Help
Set Previous Property Value

Updates a specified property with a previous value of the selected property provided by the user.

Common Internal Property Names

Deal Amount: amount
Deal Stage: dealstage
Close Date: closedate
Priority: hs_ticket_priority
1
Add Action
2
Set Get Property
3
Set Update Property
4
Save Configuration

Important Considerations

  • Always use the internal property names in workflows
  • Create properties before setting up workflows
  • Test workflows with a single record first

Best Practices

  • Group related property tracking in one workflow
  • Use clear naming conventions for workflows
  • Add notes to document workflow purpose
Rate Limits & Processing

Understanding PrevVal's processing limits and optimization strategies

Startup

• 100 requests/day
• 100 skipped/day
• 24/7 support

Professional

• 500 requests/day
• 500 skipped/day
• 24/7 support

Enterprise

• 5,000 requests/day
• 2,000 skipped/day
• 24/7 support

Ultimate

• 10,000 requests/day
• 5,000 skipped/day
• 24/7 support

Understanding Processing Types

Single Processing

For real-time property value changes during normal operations.

Workflow Settings: ✓ Re-enrollment: Enabled ☐ Batch Processing: Unchecked

Best Used For:

  • Day-to-day property changes
  • Individual record updates
  • Real-time tracking requirements

Batch Processing

For bulk historical data processing and backfilling multiple records.

Workflow Settings: ✓ Re-enrollment: Enabled ✓ Batch Processing: Checked Example Trigger: - Import completion - Mass update finished - Bulk property changes

Best Used For:

  • Initial data backfills
  • Processing up to 100 records at once
  • Historical data capture

Important Considerations

  • Batch processing counts each record as a separate request
  • Monitor your daily API limits when using batch processing
  • Consider time zones when scheduling batch processes

Best Practices

  • Test batch workflows with a small sample first
  • Schedule batch processes during off-peak hours
  • Use appropriate filters to limit batch processing scope
Create Custom Calculations

Learn how to calculate time-based metrics using PrevVal's previous value tracking

Lifecycle Stage Duration

Track how long contacts spend in each lifecycle stage.

Workflow: Stage Time Tracking Trigger: lifecyclestage changes Step 1: PrevVal Action Get previous value for: Property: lifecyclestage Store in: previous_lifecyclestage Step 2: Calculate Duration Formula: DIFF(NOW(), last_lifecyclestage_change_date, "days") Store in: days_in_stage

Best Used For:

  • MQL to SQL conversion time
  • Lead aging analysis
  • Customer lifecycle reporting

Deal Stage Duration

Monitor time deals spend in each stage of your pipeline.

Workflow: Deal Time Tracking Trigger: dealstage changes Step 1: PrevVal Action Get previous value for: Property: dealstage Store in: previous_dealstage Step 2: Calculate Duration Formula: DIFF(NOW(), last_dealstage_change_date, "days") Store in: days_in_dealstage

Best Used For:

  • Sales cycle analysis
  • Pipeline velocity tracking
  • Stage bottleneck identification

Pro Tips for Time-Based Calculations

  • Set up reporting dashboards to monitor durations
  • Create alerts for extended durations
  • Use duration data to optimize processes
  • Compare durations across different segments
Workflows to Track Property Changes

Example workflows for tracking property changes across different HubSpot objects

Contact Properties

Track changes to contact lifecycle stages and lead status.

Workflow: Contact Change Tracking Trigger: Contact property changes Branch 1: Lifecycle Stage IF: lifecyclestage changes THEN: PrevVal Action Property: lifecyclestage Store in: previous_lifecyclestage Branch 2: Lead Status IF: hs_lead_status changes THEN: PrevVal Action Property: hs_lead_status Store in: previous_lead_status

Common Properties:

  • hs_lead_status → previous_lead_status
  • lifecyclestage → previous_lifecyclestage

Deal Properties

Monitor changes in deal stages and amounts.

Workflow: Deal Change Tracking Trigger: Deal property changes Branch 1: Deal Stage IF: dealstage changes THEN: PrevVal Action Property: dealstage Store in: previous_dealstage Branch 2: Deal Amount IF: amount changes THEN: PrevVal Action Property: amount Store in: previous_amount

Common Properties:

  • dealstage → previous_dealstage
  • amount → previous_amount

Company Properties

Track changes to company status and type.

Workflow: Company Change Tracking Trigger: Company property changes Branch 1: Company Type IF: company_type changes THEN: PrevVal Action Property: company_type Store in: previous_company_type Branch 2: Industry IF: industry changes THEN: PrevVal Action Property: industry Store in: previous_industry

Common Properties:

  • company_type → previous_company_type
  • industry → previous_industry

Ticket Properties

Monitor support ticket status and priority changes.

Workflow: Ticket Change Tracking Trigger: Ticket property changes Branch 1: Ticket Status IF: hs_ticket_status changes THEN: PrevVal Action Property: hs_ticket_status Store in: previous_ticket_status Branch 2: Priority IF: hs_ticket_priority changes THEN: PrevVal Action Property: hs_ticket_priority Store in: previous_ticket_priority

Common Properties:

  • hs_ticket_status → previous_ticket_status
  • hs_ticket_priority → previous_ticket_priority

Pro Tips for Workflow Setup

  • Use folders to organize your tracking workflows
  • Set up error notifications for workflow failures
  • Review workflow history regularly
  • Document any custom property dependencies