Skip to main content

​
What routines are

A routine is a saved conversation template that IMP can replay — with the same steps, the same agent, and optionally the same or varied inputs — whenever you trigger it. Run a routine on demand from the list or from chat, or set it on a cron schedule to run automatically. Routines let you codify repeatable AI workflows: a weekly status digest, a nightly data-quality check, a customer onboarding conversation, or any pattern you find yourself asking an agent to repeat.
Routines are created exclusively from chat via Save as routine. You cannot create a routine from scratch in the Routines section — you build the conversation in chat first, then promote it. See Save as Routine in the ⋯ menu on the Chat overview page for how to save a conversation as a routine.

​
The routines list

Open Routines from the sidebar under the Build group. The list shows every routine your account can read. The toolbar has two controls:
  • Search — type into “Search routines…” to filter by name in real time. Clearing the field restores the full list.
  • Actions column — each row has a Run button and a row overflow menu (⋯) with Edit, View, and Delete.
Each row shows:
“No routines yet” appears when no routines exist or when none match your search. The empty state reads: “Save any chat conversation as a routine to run it again — on demand or on a schedule.”

​
Run a routine

Click Run on any row. The Run routine dialog opens:
  • If the routine has no input variables: “No input variables required for this routine.” Click Run now or Queue routine depending on whether the agent has a queue configured.
  • If the routine has variables: one text field per variable appears with the label and a placeholder (“Enter {variable}…”). Required fields are marked. Fill them in and click Run now or Queue routine.
On success, a toast confirms “Routine run started” (immediate) or “Routine queued” (queued). The run appears in the routine’s Runs section.
If the agent attached to the routine has a job queue configured, runs are dispatched to that queue rather than executing immediately. The dialog shows “Queued on {queue}” vs. “Runs immediately” to tell you which applies.

​
The routine workbench

Click a routine row (anywhere except the Run button) or click Edit in the overflow to open the routine’s workbench at /workflows/{id}. The workbench is a scrollable page with a section nav rail on the left. Sections, in order:
  1. Basics — name, description, and the agent that runs this routine.
  2. Access — who can see and edit the routine (Private, Public, or shared with users/teams/roles).
  3. Steps — a read-only preview of the conversation steps, with an Edit steps button that opens a sheet editor.
  4. Schedule — set or remove a cron schedule.
  5. Runs — history of past runs with status, timestamps, and retry support.
  6. Queue — the job queue for this routine’s agent; shows pending and recent jobs.
  7. Danger zone — permanent deletion (visible only if you have delete permission).
Each section is described in detail on Runs and schedules.

​
Visibility and access

Each routine has one of these visibility settings: Read access lets someone view the routine and run it; write access lets them edit steps, schedule, and configuration. The Access section in the workbench controls this.

​
Next steps

Runs and schedules

View run history, set a cron schedule, manage the queue, and delete a routine.

Prompts

Use prompt templates to parameterize routine steps.

Agents overview

The agent attached to a routine determines the model, skills, and tools available.