Configure a Salesforce Record-Triggered Flow to fire on object create and update with entry conditions and a scheduled path
domain: help.salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In Flow Builder, create a new Record-Triggered Flow and select the triggering object (e.g., Opportunity)
Set the trigger to fire when a record is created or updated; define entry conditions using the Condition Requirements section to restrict the flow to relevant records (e.g., Stage equals Closed Won)
Add an Immediate Actions path for logic that should run synchronously at record save time (field updates, record creation)
Add a Scheduled Path under Time Source (e.g., 3 days after record last modified) for follow-up automation such as sending a reminder
Use the $Record variable to access triggering record field values; use $Record__Prior to access pre-update values for changed-field detection
Activate the flow; monitor via Flow Interview Errors and the Paused and Waiting Interviews view for scheduled path failures
Known gotchas
Record-Triggered Flows with scheduled paths require the record to remain saved and matching the entry condition at the scheduled time; if the record changes before execution, the interview may be deleted
Immediate paths in Record-Triggered Flows share the triggering transaction's governor limits with any Apex triggers on the same object — combined SOQL and DML consumption must stay within limits
A flow activated without entry conditions runs on every qualifying record regardless of field values, which can cause unexpected volume and hit daily flow interview limits
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?