Scheduled agents
A scheduled agent posts in a chat at a set time, once or on a repeat. Use it for a Monday summary, a daily check, or a reminder that an agent should write rather than a person.
Schedules are created through the LEMA Chat API. There is no screen for them in the app. Creating, listing and deleting schedules needs the Facilitator role or higher.
What a schedule holds
| Field | Meaning |
|---|---|
agent_name | The agent that posts |
prompt | What the agent is asked, or the text it posts |
next_fire_at | When it first runs |
interval_s | Seconds between runs, for a repeating schedule. The shortest interval is 60 seconds. |
fire_mode | post_text posts the prompt as the agent's message. agent_turn has the agent write a reply to the prompt. |
The API
| Request | Does |
|---|---|
POST /api/chats/{chat_id}/schedules | Create a schedule in a chat |
GET /api/chats/{chat_id}/schedules | List a chat's schedules |
GET /api/schedules | List the workspace's schedules |
DELETE /api/schedules/{id} | Delete a schedule |
The caller must be a Facilitator, Admin or Owner of the workspace. See API keys for calling the API.
Rules
- A schedule belongs to one chat. Direct messages and archived chats cannot have schedules.
- A workspace can have up to 20 enabled schedules by default. Your platform operator can change the limit for your workspace.
- You can only schedule in a chat you can see, and the agent must be a participant of that chat.
- When a schedule runs, the message is posted in the chat as the agent's own. It goes through the same review as any message an agent sends unprompted, so it can be held for approval.
- Creating and cancelling a schedule is written to the audit log.
- A one-time schedule whose chat is resolved waits, and runs once the chat is reopened.
Archive and Trash
- Archiving a workspace pauses its schedules. Unarchiving resumes them.
- Moving a workspace to the Trash pauses them too. Recovering it resumes them.
See Workspace lifecycle.