post_text_message_templates_merge
Preview how a text message template looks when merged with multiple recipients' names and phones. Returns the rendered message without sending it.
Instructions
Merge a text message template with multiple recipients. (POST /textMessageTemplates/merge) Despite the name, this does NOT send anything — verified live 2026-09: firing this at a real phone number produced no delivery and no new record in list_text_messages, only a rendered string back ({"mergedTemplate": "..."}). It's a preview/render utility for the edge case of one text greeting multiple recipients at once (e.g. "Hey Bob, Alice and Carol..."), not an actual send.
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": {
"templateId": "<templateId>"
},
"name": "post_text_message_templates_merge"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| personId | No | Person ID to use for merge fields like %contact_name%. | |
| extraBody | No | Extra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is. | |
| extraQuery | No | Extra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is. | |
| recipients | No | List of recipients of this text message. | |
| templateId | Yes | The ID of the text message template. |