Skip to main content
Automation is optional. Every compatible agent can begin with a manual run, then add the trigger that best matches how work arrives.

​
Available run conditions

Manual

Start work when a person is ready.

Email inbox

Receive documents through a dedicated Layest address.

Schedule

Start compatible work on a recurring cadence.

File event

Start when a file is added or updated in a connected folder.

​
Email intake

Create an inbox from the agent’s Setup page. Give it a recognizable name, then copy the dedicated address for the people or systems that should submit files. Manual uploads remain available. Pause the inbox when you temporarily want to stop new email-triggered runs.

​
Scheduled work

Reusable schedules can run daily, weekly, or monthly at a chosen local time and time zone. Compatible agent configurations select the schedule they need. Examples include:
  • a recurring report
  • an import from a configured source
  • a BMD export of approved, not-yet-exported invoices

​
Connected folders

First connect a supported storage provider. Then choose a folder, select the file-event rule, and decide whether existing files should be included. A folder intake can react when:
  • a new file is added
  • a file’s content is updated
  • either event occurs
Pause, resume, or retry a folder intake from Setup without affecting the files in the external service.

​
Design automation around exceptions

Before enabling automation:
  1. prove the workflow with manual examples
  2. confirm the source and destination
  3. assign a reviewer
  4. decide which statuses need monitoring emails
  5. test one real event
  6. document what to do when a connection is disconnected
Optional triggers never make an otherwise ready agent blocked. A configured trigger can still need attention when its source, output, or connection is missing.