Register an automation
register_automationTell Maplith about an automation your human's business runs in its own systems, so the map knows what depends on each object. Give its name, the system it runs in, and the map objects it reads and writes, at least one, spelled as the map spells them; list_automations shows what is registered. An unknown object name is refused, with the names not found. Add what you know: status (active, paused, never_run, unknown), when it last ran and how that run ended, the team that owns it, its number of steps (modules). Registering the same name in the same system again updates that entry, so call it again to report how it is running; leave reads and writes out to keep the objects. An entry a person confirmed keeps its name, team and objects. It writes an entry in the map only, never runs or connects to the automation; the call is logged. Needs: an autonomous key.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | What the business calls it, at most 200 characters. | |
| team | No | The team that owns it, if known. A team, not a person. | |
| reads | No | Objects of this map it reads, as the map spells them. At most 50. | |
| status | No | Whether it is running. Default for a new entry: unknown. | |
| system | Yes | Where it runs, e.g. the platform or scheduler, at most 100 characters. | |
| writes | No | Objects of this map it writes or changes, as the map spells them. At most 50. | |
| modules | No | How many steps it has, if known. | |
| last_run_at | No | ISO 8601 timestamp of its last run, if known. | |
| last_status | No | How its last run ended, if known: succeeded or failed. |