Overview
Automations and conditional fields now come with a suggested name. The name is built from what you configured. Anyone opening the list understands what each one does without opening its setup.
Until today, a new automation started with an empty name. The person who created it knew what it did. Anyone inheriting the process, or the same person months later, had to open each one. In a pipe with dozens of automations, the list stopped being readable.
What's new?
- Suggested at creation. The name comes from the trigger and action you configured. For conditional fields, it comes from the condition and the affected field.
- Works on what you already have. When editing an existing automation or conditional field, ask for a suggested name and bring the whole pipe up to the same standard.
- Both objects. Automations and conditional fields.
- Always editable. It's a suggestion, not a rule. Prefer your own naming? Just edit it.
How does this help?
- A readable list. You understand what each automation does without opening its setup.
- Handoffs without loss. Whoever takes over the process understands its structure without depending on the original builder.
- A standard from day one. Names follow a consistent convention, and you adjust them whenever you want.
Use cases
Financial operations analyst managing accounts payable
Invoices enter the triage phase and move to approval based on cost center. Each cost center has its own automation. With suggested names, the list shows the difference without opening any of them:
[Triage] Card enters phase (Cost center = Marketing) → Move card
Customer support leader managing incident response
An incident pipe sends alerts when a card is overdue. The suggested name says what the automation does:
[Overdue card] Alert triggered → Send email template
Anyone on the team finds the right automation when investigating a delay.
People operations specialist managing employee onboarding
The onboarding form shows the equipment field only for technical roles. The conditional field gets a name that describes the rule:
[Show] Role is Technical → Required equipment
The HR team reads the form without external documentation.
Most relevant for
- Pipe admins and process builders
- Operations leaders
- Process and governance managers
Plans and availability
This feature is being rolled out gradually across organization accounts and is available for immediate use at no extra cost.
