Skip to main content
Find Record Changes answers a different question than Find Records. Find Records tells you what a record looks like now. Find Record Changes tells you what happened to it, the close date that moved twice this month, the stage that slipped back, the owner who changed last week. It selects records exactly the way Find Records does, then returns those records’ changes instead of the records themselves. It’s read-only. Like Find Records, it gathers data but doesn’t take an action, so it doesn’t satisfy a workflow’s requirement to include at least one action step, pair it with a Slack message, an email, an agent, or a CRM write.

​
Before you start

Change history is recorded going forward only. There is no backfill. A workspace that just turned this on has no history until records start changing, so a step that looks back 90 days will return nothing on day one and fill in from there. If a step comes back empty, this is usually why. Only accounts and deals are history-tracked. Other object types have no change history to read.

​
Build it

  1. Add a Find Record Changes step anywhere after the trigger.
  2. Choose the object type, Account or Deal.
  3. Pick the records: describe them in plain language with AI, or select them precisely with Logic conditions, a list of record IDs, or external IDs. Set one, not several.
  4. Set how many records to select, between 1 and 100.
  5. Optionally narrow what comes back: a time period, a single field, and a per-record changes limit.

​
Field reference

​
Using the results

The step returns one row per change, and each row carries: Reference the rows as {{<step-id>.changes}}, feed that into a loop to act on each change. Two more values come with it: {{<step-id>.count}}, the number of changes returned, and {{<step-id>.truncated}}, which is true when a limit dropped rows. Check truncated before you describe a result as complete; if it’s true, raise the changes limit or narrow the period.

​
In practice

A Monday-morning schedule selects every open deal closing this quarter, then a Find Record Changes step scoped to the close date field over the last 30 days pulls every date move. A loop posts one Slack line per slip: deal, old date, new date, who moved it. Nobody has to open a report to see which dates are drifting.

​
Beyond workflows

The same change history is available from Claude or ChatGPT through the find_record_changes tool on the Clearskies MCP server, so you can ask what moved on an account in conversation instead of building a workflow for it. Questions? We’re here to help at support@clearskies.cc