HubSpot Property Tracing

Introduction

When you see a HubSpot property change that came from AskElephant and you need to know which workflow did it, work through the four steps below.

1. Check Workflow History

Open Workflow History in AskElephant.
Filter by the timestamp shown in HubSpot's property history.
Review runs from that window.
Look for HubSpot action nodes that updated a deal. Confirm which property changed.
If a node shows errors or partial failures, open it to read the specific error message.

2. Verify the Trigger

Identify whether the run started from Deal Created or Deal Updated.
For Deal Updated, note which property the trigger watches — that's often why the workflow fired.

Understanding the trigger usually explains unexpected updates.

3. Reproduce on a Test Deal

Use a test deal to validate your findings.
Make a small update to the property you suspect is being watched.
Observe which workflows enrol and run.
Confirm which node is performing the property update.

4. Fix and Re-Test

If outputs were blank or incorrect, check the prompt nodes or variable references feeding the update.
Confirm the HubSpot Agent has write permissions.
When pulling HubSpot data from previous workflow steps, use a HubSpot Agent node — not a Run Prompt node. Run Prompt nodes can't access HubSpot context from earlier steps and will fail to retrieve the data reliably.
Run a small test to confirm the fix.

Pro tip. Always use HubSpot Agent nodes when you need to reference HubSpot data from a prior step.

HubSpot — setup, capabilities, and the broader HubSpot troubleshooting section.
Testing Workflows Without Activating Them — test-deal best practices before step 3.

Need More Help?

Reach the AskElephant support team by clicking the chat button in the bottom right corner of your screen, emailing [email protected], or using @askelephant support in your dedicated Slack channel.