List schedule triggers
well_list_schedule_triggersList the events Well can start a routine on, each with what it means and the details it carries.
Use it when the user wants a routine to start each time, or as soon as, something happens, instead of at a set time ("send me a poem at 1:45am") or on a rhythm, which need no trigger. Each entry carries a trigger (the value for well_create_schedule's trigger_name), a description of what happened and when it fires, and params (the event details the run receives, by name). The list is empty when Well sends no event yet.
When one entry fits what the user described, create the routine with that trigger_name and no cron_expression, and describe the event in the cadence_label in plain words. When none fits, say that Well cannot start a routine on that event yet and offer a clock rhythm. Never say a trigger name to the user.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | No | Target workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| success | Yes | ||
| triggers | Yes | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |