Messaging: Send to contact
messaging_send_to_contactOne-step send for voice-style requests: 'send a WhatsApp to Julien saying I'm 10 minutes late'. Resolves the recipient like messaging_resolve_recipient and sends the text ONLY when exactly one person matches (existing conversation or contact). When lookup is incomplete or several people match, nothing is sent and the candidates are returned so you can ask the user which one. The user must have stated the message content; do not invent it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"provider": "<provider>",
"name": "<name>",
"text": "<text>"
},
"name": "messaging_send_to_contact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | How the user refers to the recipient. | |
| text | Yes | Exact message text the user asked to send. | |
| inbox_id | No | Required for Facebook: exact personal or PAGE_<id>_INBOX inbox.id from facebook_list_inboxes. Preserves the sending identity. Omit for other providers. | |
| provider | Yes | Messaging provider named by the user. LinkedIn recipients use linkedin_resolve_person + linkedin_start_conversation instead. | |
| account_id | No | Optional Nilyo connection ID (unipile_account_id from list_connected_accounts). Required when the user has several accounts for the provider: pick the one the user named. | |
| recipient_user_id | No | Exact provider user ID chosen by the user after an ambiguous result; skips name matching. |