Automations

Lextree does a few things on its own after you save a record — filling in fields, recording timeline entries, and offering to create events or workflows. None of it happens instead of your save, and none of it creates anything visible without either following rules your admin set up or asking you first.

The Rule Behind Every Automation

Everything on this page happens after a save completes, never in place of it. An automation can add to what you did — it can’t hold up the save, redirect it, or fail it. If an automation ever breaks, your record is already saved; the automation is the layer that bends.

Fields and Timeline Entries

Some fields compute their own values from elsewhere on the record — a date offset from another date, a total across related records, a value carried over from a parent. These are custom fields configured to derive rather than accept typed input. When one looks wrong, fix the field it derives from; the calculated field follows.

Some timeline entries record themselves the same way — an expiration date passes and Expired appears with no one watching. An automatic entry is an ordinary timeline entry once it exists: correct it the same way you’d correct anything else on the timeline.

Suggestions Wait for Your Yes

Admins can attach conditions to event and workflow templates — “when a record like this gets a renewal date, offer the renewal-reminder event.” When a record you’re working with matches one of those conditions, Lextree suggests the event or workflow rather than creating it outright. Accepting a suggestion creates it, exactly as if you’d built it yourself; declining dismisses it. Nothing is ever created from a suggestion without your yes. That’s what separates a suggestion from the fields and timeline entries above, which just happen on their own.

The Post-Save Suggestion Dialog

The most common place you’ll meet a suggestion is right after you save a record. If the record matches a condition your admin configured, a dialog opens over the record offering the event or workflow — accept to create it, decline to dismiss it.

You don’t have to decide immediately. Closing the dialog without choosing doesn’t lose the suggestion; it moves to the notifications bell, where opening it reopens the same accept-or-decline choice.

An accepted suggestion behaves exactly like something you created by hand: an accepted event suggestion produces a normal event on the record’s calendar, and an accepted workflow suggestion produces a normal workflow instance you can open and work.

Suggestions After Bulk Actions

Suggestions aren’t limited to one record at a time — importing or bulk-updating many records at once can trigger the same conditions across all of them, and Lextree gathers the results instead of interrupting you record by record.

After Importing Records

When an import finishes, its summary gathers every suggestion your new records triggered into one place. A thousand imported licenses that all match a renewal-reminder condition can become a thousand renewal reminders in a few clicks — right from the import summary, not one dialog per record.

After a Bulk Update

Editing many records at once works the same way. The bulk-update drawer shows one card per matching template, labeled “Create X for N of M selected records.” Accepting a card confirms the count first, since one accept creates an event or workflow for every matched record in that batch — not just the one you’re looking at.

Who Gets Workflow Suggestions

Event suggestions are available on every plan, since events are too. Workflow suggestions require Business or Enterprise , because workflows are gated at those tiers. On a plan without workflows, only event suggestions appear in the dialog, the bell, and the bulk summaries.

For how these conditions get set up in the first place, see Automation setup.