For the complete documentation index, see /llms.txt. The full corpus is available at /llms-full.txt. Most pages have a raw markdown variant; append .md to the URL or send Accept: text/markdown.

Docs  |  User Guides

Automations

Run Assist workflows unattended. An Automation pairs a Skill with a trigger — a schedule, or an import event — so that reports, data imports, or analyses happen automatically without anyone needing to start a session.

What you can do with Automations

  • Generate periodic reports: Produce a batch summary or campaign report every Monday morning, ready for the team before standup.
  • Stage data imports on a schedule: Automatically stage incoming instrument data for review at a fixed time each day.
  • React to incoming data: Trigger an analysis or notification as soon as an import succeeds or fails, instead of waiting for the next scheduled run.
  • Reduce repetitive work: Any analysis you would otherwise run by hand on a recurring basis can be turned into an Automation.

Creating an Automation

  1. Open the Automations page from the sidebar.
  2. Click New Automation.
  3. Give the automation a descriptive name.
  4. Select a Skill — this determines what the automation does when it runs.
  5. Choose Outputs — select whether each run produces a Report, an Import Preview, or both. Every run also creates an Assist session you can review.
  6. Set a Trigger — either a schedule (daily, or weekly on a specific day) or an import event: an import succeeded, an import failed, or a bulk import completed. For import event triggers, use Mappings to limit the automation to imports that use specific ingestion mappings; the default is Any mapping.
  7. Choose whether to Notify when finished — leave it on to get a notification each time the automation completes.
  8. Click Save.

Managing Automations

Select any automation from the list to open its detail panel. From here you can:

  • Edit configuration — change the name, skill, outputs, or trigger at any time.
  • Duplicate — create a copy of an existing automation as the starting point for a new one.
  • Enable or disable — toggle the automation on or off without deleting it.
  • Run now — trigger a one-off run immediately, outside the normal schedule.
  • Take over — make future runs use your account instead of the account the automation runs as now. Take over is not available if the automation already runs as you.
  • View run history — see past runs with their status, trigger source, duration, and links to the resulting report or session.
  • Delete — permanently remove an automation you no longer need.

Finding automations

The list page has two tabs: Running as me shows only the automations that run under your account, while All shows every automation in the organization — useful to see what recurring analyses colleagues have set up and to avoid duplicating effort. Filter the list by trigger, outputs, or the account an automation runs as, and search by name.

Halted Automations

If an automation fails on consecutive runs it is automatically halted to prevent repeated failures. A halted automation shows a warning banner explaining when it stopped and why. To resume, fix the underlying issue in the linked Skill, then use Run now to confirm it succeeds — the automation re-enables on the next successful run.