changedInput schema / properties / actions / description
Previous value: -"Then: 1 to 3 actions, run in this order on the record that met the rule."New value: +"Then: the actions, in order."
changedInput schema / properties / actions / items / properties / arguments / description
Previous value: -"For a change action: one item of that action's propose_ tool, for the record that met the rule. Use {record.id} as its id and leave type out for the rule's own record type. To act on the contact of a record, give type contact with {record.contact} as its id; on its deal, type opportunity with {record.deal}; on its job, {record.job}. To act on what an earlier action of the rule made (create_record, convert_estimate, convert_lead), use {action1.id} for the first action. To give a task or record to the owner of the record that met the rule, use {record.owner} as its user. For assign_owner, users is a list of user ids that take turns, one per record. For notify: to is owners or the emails of members of the CRM Connector account (at most 5), text what to tell (at most 900 characters) and optionally subject; it tells at most 50 times a day. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts. For email_contact: subject, body, sender_name (the From name shown, 2 to 60 characters) and reply_to (the address replies go to), both required. The subject and body may use {contact.first_name}, {contact.name}, {record.name}, {organisation}; the address it goes to is always the contact's own."New value: +"For a propose_ action: one item of that tool with {record.id} as its id; {record.contact}, {record.deal}, {record.job}, {record.owner} and {action1.id} name other records. notify: to, text, subject. email_contact: subject, body, sender_name and reply_to; ask the person for the last two."
changedInput schema / properties / actions / items / properties / kind / description
Previous value: -"The action the rule applies by itself: set_fields to set or empty fields of the record, create_record to make a record of another type, notify to tell people of the CRM Connector account in the app and by email, or a change action named as its propose_ tool without the prefix (update_fields, move_stage, assign_owner, add_note, add_task, update_task, log_activity, add_line_item, link_records, unlink_records and the others). One more is carried out by CRM Connector itself and is only switched on through the approval page: email_contact (a short email to the email address of the record's contact)."New value: +"set_fields, create_record, notify, email_contact (approved on its page only), or a propose_ tool's action without the prefix, such as add_task."
removedInput schema / properties / actions / items / properties / kind / enum
Removed value: -[
- "set_fields",
- "create_record",
- "notify",
- "update_fields",
- "move_stage",
- "assign_owner",
- "add_note",
- "add_task",
- "update_task",
- "log_activity",
- "add_line_item",
- "send_record",
- "convert_estimate",
- "convert_lead",
- "link_records",
- "unlink_records",
- "create_item",
- "update_item",
- "set_item_state",
- "move_item",
- "add_tag",
- "remove_tag",
- "add_follower",
- "remove_follower",
- "add_to_workflow",
- "remove_from_workflow",
- "update_note",
- "send_message",
- "update_conversation",
- "record_payment",
- "change_consent",
- "void_record",
- "send_document",
- "email_contact"
-]
addedInput schema / properties / actions / items / properties / kind / maxLength
Added value: +40
changedInput schema / properties / actions / items / properties / set / description
Previous value: -"For set_fields: field keys and their new values. For create_record: the fields of the new record, such as its contact as {record.id}. A date may be {today} or {today+3} (three days after the rule acts). {record.field:Amount} is the value a field of the record that fired holds when the rule acts."New value: +"For set_fields and create_record: field keys and values. Values may use {record.id}, {today}, {today+3} and {record.field:Amount}."
changedInput schema / properties / actions / items / properties / type / description
Previous value: -"For create_record: the record type to make, such as opportunity."New value: +"For create_record: the record type to make."
changedInput schema / properties / apply_to_existing / description
Previous value: -"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."New value: +"Also act once on records that already match."
changedInput schema / properties / conditions / description
Previous value: -"Only if: at most 5 conditions on the same record, all of which must hold. Leave it out when the rule always acts."New value: +"Only if: conditions that must all hold."
changedInput schema / properties / conditions / items / properties / field / description
Previous value: -"The field key, as describe_record_type names it."New value: +"The field key."
changedInput schema / properties / conditions / items / properties / value / description
Previous value: -"The value to compare with; not for empty and not_empty, and a number for above and below."New value: +"Not for empty and not_empty; a number for above and below."
changedInput schema / properties / conditions / items / properties / values / description
Previous value: -"For one_of: the values the field may hold."New value: +"For one_of."
changedInput schema / properties / name / description
Previous value: -"A short name for the rule, as the customer would call it."New value: +"A short name for the rule."
changedInput schema / properties / replaces / description
Previous value: -"Optional: the id of an earlier automation of the same system that this rule replaces once it is approved."New value: +"Optional id of an automation this rule replaces once approved."
changedInput schema / properties / system / description
Previous value: -"Which AI agent: the system's id from get_ai_agent_options, 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."New value: +"The AI agent: its system or connection name."
changedInput schema / properties / trigger / description
Previous value: -"When the rule acts: created (a record of the type is made), becomes (a field gets a value, such as a deal becoming won), changes (a field changes in any way), date_reached (a date field of the record is a number of days before or after today, such as 3 days before the due date), unchanged_for (the record has not changed for a number of days, such as a deal stuck in a stage), tag_added or tag_removed (a tag is put on or taken off the record)."New value: +"When the rule acts."
changedInput schema / properties / trigger / properties / days / description
Previous value: -"For date_reached: days after the date, negative for before it (-3 is three days before the due date, 30 is thirty days after it, 0 the day itself). For unchanged_for: the days without a change, at least 1."New value: +"For date_reached: days after the date, negative for before. For unchanged_for: days without a change."
changedInput schema / properties / trigger / properties / field / description
Previous value: -"The field key, as describe_record_type names it. Needed for becomes, changes and date_reached (the date field); for unchanged_for only with a value it must hold; for a tag trigger left out unless the system keeps tags in a field of its own."New value: +"The field key. For becomes, changes and date_reached."
changedInput schema / properties / trigger / properties / kind / description
Previous value: -"created, becomes, changes, date_reached, unchanged_for, tag_added or tag_removed."New value: +"created, becomes (a field gets a value), changes, date_reached, unchanged_for, tag_added or tag_removed."
changedInput schema / properties / trigger / properties / value / description
Previous value: -"For becomes: the value the field must get, as the system stores it; leave it out for any value. For unchanged_for: the value the field holds while the record stands still, such as a stage. For tag_added and tag_removed: the tag."New value: +"For becomes: the value it gets. For unchanged_for: the value it holds. For a tag trigger: the tag."
changedInput schema / properties / trigger / properties / yearly / description
Previous value: -"For date_reached: the date comes round every year, such as a birthday."New value: +"For date_reached: every year, such as a birthday."
changedInput schema / properties / type / description
Previous value: -"The record type, as get_ai_agent_options lists it: contact, opportunity, invoice, estimate, job, appointment."New value: +"The record type, such as contact or invoice."