Rules you can read out loud
Automation earns its place when it removes work nobody wanted to do. It becomes a liability when nobody can remember what it does. Golden Porch keeps rules in plain conditions and actions, and keeps a record of everything they touched.
Conditions and actions, nothing else
A rule is a trigger, some conditions, and one or more actions. There is no scripting layer, no expression language to learn, and no situation where understanding what a rule does requires a developer.
The constraint is deliberate. Rules that anyone on the team can read are rules that get reviewed, corrected and retired instead of quietly accumulating for years.
- Triggers on record change, stage change, time elapsed or inbound event
- Conditions on any field, including custom ones
- Actions: assign, notify, create task, update field, call a webhook
Test before it touches anything
The failure mode of CRM automation is a rule that quietly does the wrong thing to several thousand records. Three things guard against that.
Dry run
Run a rule against live data without applying it. You get the list of records it would have matched and the changes it would have made, before deciding.
Rate limits
Rules have a ceiling on how many records they can affect in one run. Hitting the ceiling pauses the rule and notifies its owner rather than continuing.
Audit log
Every firing is logged with the record, the rule version and the resulting change. When something looks wrong, you can trace it rather than guess.
What teams usually automate first
In practice the first handful of rules are almost always the same, and they are the ones with the clearest payback:
- Lead assignment — route inbound by territory or round-robin, so nothing sits unclaimed
- Stall alerts — notify the owner when a deal passes the ageing threshold for its stage
- Missing next step — create a task when a deal advances without one scheduled
- Out-of-office handover — temporarily reassign open work when an owner is away
- Renewal reminders — open a task a set period before a contract date
Worth knowing: teams that automate aggressively on day one usually end up unpicking it. Rules encode assumptions about a process, and a process you have only just moved into a new system is not yet stable enough to encode.
Webhooks and the API
When a rule needs to reach outside Golden Porch, the webhook action posts the record to an endpoint you control. Combined with the REST API, that covers most integration work without needing a dedicated connector.
Ownership and review
Every rule has a named owner and a last-reviewed date. Rules that have not fired in ninety days are listed separately, which is usually enough of a prompt to delete the ones that no longer apply.
Next: what all of this produces
Clean records and consistent stages are only worth the effort if the reporting reflects them.
Reports