When a workflow enrolls one record but the Edit record action updates an associated record, there is currently not enough visibility in the workflow action logs to see exactly which associated record was changed.
This is especially relevant because the Edit record action can target either the enrolled record or an associated record.
Today, the workflow action logs are documented as showing high-level information such as the record, diagnose/details, action, event, and time, and HubSpot also notes that workflow action log data is stored as high-level action log data such as object ID, event type, and action type.
Requested improvement:
-
When an Edit record action updates an associated record, show the specific associated record ID and name in the action log
-
If multiple associated records were updated, show all affected records
-
Include this detail both in the in-app log view and in exported action log CSVs
-
Ideally, make the affected target record searchable in workflow history/action logs as well
Example use case:
A contact enrolls in a workflow, but an Edit record action updates the associated company, deal, task, or custom object. The workflow history confirms that the action ran, but it is difficult to verify which associated record was actually changed without manually investigating associations and property history.
Why this matters:
-
Faster troubleshooting for workflows that act across associated objects
-
Better auditability for automation changes
-
Less manual investigation when multiple associated records exist
-
More confidence using Edit record in complex CRM data models
There are already related requests around improving workflow action log visibility and searchability, which suggests this would solve a real customer pain point.