ConnectorToolMessaging
What makes a Connector tool a messaging tool (1.60.0): the action, the channel and the arguments that carry the recipient and the text. Every call of such a tool writes a Message beside its Run. A send tool was refused in 1.60.0 (founder question Q2, taken at its recommended default); from 1.61.0 every send runs under the consent check of the send path, the exec role asking the api (check_send_consent) before it sends, a refusal ending the call refused with recipient_opted_out.
An object with 5 fields.
Fields
body_argumentstringrequiredThe input property that carries the text.
recipient_argumentstringrequiredThe input property that carries the recipient: a number, an address, a channel or a chat. A binding fixes it or takes it from a variable, so the model never chooses it (channels.md section 2, rule 2).
subject_argumentstring or nullrequiredThe input property of an email subject; null for other channels.