Patch WhatsApp flow text
patch_whatsapp_flow_textRewrite wording inside a WhatsApp Flow draft, and nothing else. Each patch is a JSON pointer (from get_whatsapp_flow: the component's path plus "/" plus the property, e.g. /screens/0/layout/children/1/label) and the replacement string; at most 20 per call, applied all or nothing. Refused outright, with the path named: a pointer that does not land on a text property (a screen id, an action name, a component type, a payload key). A flow that is not a draft cannot be patched at all; a published flow is superseded by a new draft. A value that holds a ${...} reference is a binding, not wording, and is left alone. lock_version is required and must be the one get_whatsapp_flow returned for this flow: it proves the patch was written against the document as it stands.
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": {
"flow_id": "<flow_id>",
"patches": "<patches>",
"lock_version": "<lock_version>"
},
"name": "patch_whatsapp_flow_text"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| flow_id | Yes | ||
| patches | Yes | ||
| lock_version | Yes |