Leave context inside the workflow.

A strange delay. An unusual enrollment branch. A webhook nobody wants to touch. Without context, ordinary maintenance turns into detective work.

In the June 15 Spotter issue, I wrote about using workflow comments to keep the explanation close to the action itself.

Three notes worth leaving

• The reason: explain the edge case behind an unusual branch.
• The review: flag the enrollment criteria for another person to check before activation.
• The change: record what changed in a live workflow and why.

The full issue also covered HubSpot’s Agent CLI announcement at the time. Read the original for that dated product context.