Working with Lyric
Workflows and scheduled jobs
A workflow is recurring work Lyric plans and performs itself, on a schedule or when something happens in a connected application. You describe what to accomplish; Lyric decides how. Workflows are available on Lyric Max, Lyric Teams and Lyric Enterprise.
Creating a workflow
Select New workflow on the Workflows page, or start from a template. A workflow has the following parts.
| Part | Question it answers | What you set |
|---|---|---|
| Frequency | When should this workflow run? | Schedules: the days of the week, one or more times, an optional window and the time zone |
| Triggers | What triggers this workflow? | Events in your connected applications, chosen from the connectors you have configured |
| Objectives | What should Lyric accomplish? | A numbered list of outcomes |
| Instructions and constraints | How should Lyric approach the work, and what boundaries must it respect? | Optional instructions, exceptions and restrictions |
| Autonomy | How should Lyric handle each run? | Autonomously, Ask first or Manual, as for a task |
| Verification | How does Lyric confirm the objectives were achieved? | Automatic by default, or the specific evidence you require |
| Notify | Who should hear about each run? | You and your contacts; in an organization, also its people, its teams, its administrators or everyone in it |
A workflow does not have steps. Lyric plans each run from the objectives, instructions and what it knows at the time.
Autonomy
| Choice | What Lyric does | Autonomy level | Action minutes per minute of work |
|---|---|---|---|
| Autonomously | Performs the work on its own, without asking for approval | Delegate | 1.00 |
| Ask first | Prepares the work and asks for your approval before consequential actions | Assist | 0.65 |
| Manual | Investigates and reports, while you take every action yourself | Observe | 0.25 |
Each run is performed, and consumes action minutes, at the autonomy level of the workflow's choice. In an organization, administrators may allow fewer choices. A workflow keeps its choice if your plan changes, and can be changed only to a choice open to you.
Triggers
Triggers come from the applications you have connected. A real-time trigger fires as soon as the application reports an event. A polling trigger fires when Lyric checks the application and finds a change. A workflow can have several triggers, and a frequency as well.
Verification
By default, Lyric determines the evidence of success from the objectives and the policies that apply. For consequential work, require specific evidence instead, and choose what happens if verification fails:
- Retry or replan when it is safe to do so.
- Leave the run incomplete and notify you. This is the default.
- Request approval before continuing.
Verification cannot override policies, autonomy settings or approval requirements.
Workflows in an organization
Administrators decide whether people may create workflows, whether workflows can be shared within the organization, and which templates are recommended. See Workflows, webhooks and admin keys.
Workflows and usage
Each run consumes action minutes at the rate of the workflow's autonomy level, and is reported under Workflows in the usage panel. While a run is in progress it occupies one of your concurrent task places.
Related pages
Last updated October 28, 2026