Propose an automation
propose_automationAI Agents (inside one system): Use when the customer wants something to keep happening by itself inside one system on AI Agent (not for a one-off change: use propose_changes), such as "when a deal is won and the amount is above 5,000, add a kick-off task for the owner and a note". It turns that into one fixed rule on one record type: when (trigger), only if (conditions), then (actions). Before calling it, describe the rule in plain words (when, only if, then, and whether it also acts on records that already match) and get a yes. Nothing runs yet: the answer gives the rule as one sentence, how many records it would have acted on in the last 30 days with examples, and an approval link. Share that link: the rule only starts once the customer approves it there, and from then on the platform runs it again and again without asking. Use describe_record_type for the field keys; each action is one of the actions of propose_changes (set_fields, add_note, add_task and so on), with the values that action takes there. Pass replaces with an automation id to change an existing rule. A rule only acts inside that one system: to sync records between two systems, use an integration (plan_integration). It never deletes and never records a payment.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | A short name for the rule, as the customer would call it. | |
| type | Yes | The record type, as list_ai_systems lists it: contact, opportunity, invoice, estimate, job, appointment. | |
| system | Yes | Which AI agent: the system's id from list_ai_systems, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself. | |
| actions | Yes | Then: 1 to 3 actions, run in this order on the record that met the rule. | |
| trigger | Yes | When the rule acts: created (a record of the type is made), becomes (a field gets a value, such as a deal becoming won), or changes (a field changes in any way). | |
| replaces | No | Optional: the id of an earlier automation of the same system that this rule replaces once it is approved. | |
| conditions | No | Only if: at most 5 conditions on the same record, all of which must hold. Leave it out when the rule always acts. | |
| apply_to_existing | No | Also act once on the records that already match when the rule is switched on. Off by default: the rule then only acts on what happens from now on. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| name | Yes | ||
| rule | Yes | ||
| type | Yes | ||
| notice | No | ||
| status | Yes | ||
| examples | Yes | ||
| sentence | Yes | ||
| systemId | Yes | ||
| warnings | Yes | ||
| lastRunAt | Yes | ||
| approveUrl | Yes | ||
| systemName | Yes | ||
| pauseReason | Yes | ||
| firings30Days | Yes | ||
| matchedLast30Days | Yes |