Update Pending Reply
update_pending_replyPending Replies: change one reply by reply_id: its draft (replaces; null clears), summary, channel, category, received_at, person (person_id, or person_name linked only on one match), source, or status pending (reopen / unsnooze) or snoozed with snooze_until. Unknown or other-user reply_id returns not_found. To mark it sent or dismissed use resolve_pending_reply. Never sends anything. Requires API key or OAuth with context.write. ($0.10; API key required)
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": {
"reply_id": "<reply_id>"
},
"name": "update_pending_reply"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| draft | No | The reply text to send later, max 20,000 characters. Replaces the saved draft; empty or null clears. Alias: draft_message. | |
| source | No | The email the reply answers, as ids only (e.g. a search_gmail id is a message_id). Never a subject, sender or text. On update, null clears it. | |
| status | No | Reply state, e.g. unsent. | |
| channel | No | Where to reply: whatsapp, email, sms, call, imessage, telegram, instagram, facebook, signal, linkedin, twitter, slack, reddit, teams, work_email, zoom, dayze, other; the platform the conversation is on (a Reddit thread is reddit, an Instagram group instagram). Default email when source is set, else other. | |
| summary | No | One line (max 280) in your own words: what the reply is about. Never paste the email body, subject line or sender address. | |
| category | No | Reply category: personal or work, e.g. work. | |
| reply_id | Yes | From create_pending_reply or get_pending_replies. | |
| person_id | No | Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809. | |
| request_id | No | Client idempotency key (retries return original result). | |
| person_name | No | Contact name when there is no person_id, e.g. Alex Chen. | |
| received_at | No | When the message arrived, as ISO date-time, e.g. 2026-10-17T15:30:00Z. | |
| snooze_until | No | ISO date-time, with status snoozed. | |
| draft_message | No | Alias for draft. | |
| idempotency_key | No | Alias for request_id. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reply | Yes | One reply the user owes (Inbox → Pending Replies). Dayze never sends it. | |
| account | No | The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer. | |
| message | Yes | ||
| provenance | No | Which connector wrote the record and which connected Dayze account received it. | |
| person_link | No | Whether a contact was linked. Linked only on one resolve_person match or an owned person_id. | |
| source_saved | Yes | ||
| changed_fields | Yes | ||
| life_state_rebuilt | Yes |