Setting an automation’s Runs on to Both (Person and Contract) used to strip
the Steps panel down to two options — Time Delay and Send Webhook. Everything else
disappeared, so the only way to build a real workflow was to pick one record type
and build the automation twice.
The Steps panel now offers the combined set: every action available on a Person
automation, and every action available on a Contract automation. Each one is
labelled Person only or Contract only where it applies to just one kind of
record, in the left-hand panel, in the canvas + menu, and in the step’s own
Action Type dropdown — so you can see what a step will act on while you are placing
it, rather than finding out later.
This works because of the recent change to how these runs behave: a Both automation
receives one record per run, and an action that cannot apply to that record is
recorded as skipped while the run carries on through its remaining steps. A step
labelled Contract only sitting in a workflow that also enrolls people is no
longer a problem — it simply does nothing on the person runs.
Two things are unchanged. Conditions and Loop are still available only when
Runs on is set to Person or Contract. And automations that run on People only or
Contracts only behave exactly as before.