Email · reply_email
Reply to an email
Draft and send a reply inside the original thread.
- Price
- included
- Requirements
- Gmail or Outlook
- set it up in Settings → Integrations
- Human approval
- Yes, by default
- outside-facing write: a human validates
- Reliability
- Verified
- stable · 0.4 s
Input
| Field | Type | Description |
|---|---|---|
| replies | array | Batch reply: the FULL list of replies to send in one call (preferred whenever there is more than one). Each item takes the same fields as a single reply. When provided, the top-level single-reply fields are ignored. |
| emailId * | string | The email ID returned by read_emails |
| body * | string | The reply body in plain text. Write a complete, professional email. |
| replyAll | boolean | Whether to reply to all recipients (default: false, reply only to sender) |
| to | array | Follow-up in thread: the prospect's address(es) that receive the reply to OUR sent e-mail (emailId = sentItemId from send_email / lastSentItemId from list_prospects). |
| prospecting | boolean | true for a cold follow-up: the body is checked before sending and refused with the list of problems otherwise. |
| aiDisclosure | boolean | With prospecting: require the AI-agent disclosure in the body (default true). |
| prospectId | string | Single follow-up: prospect id to mark contacted at the real send. |
| angle | string | Single follow-up: short label of the angle. |
| mailbox | string | Optional: address of a SHARED mailbox (e.g. sav@company.fr) the connected account has access to. Omit to use the connected account's own mailbox. Requires the shared-mailbox permission on the Outlook connection; a 403 means the connection must be redone with it. |
| intent | string | Type of the customer request this message answers, one of: info_produit, conseil, livraison, garantie, retour, reparabilite, reclamation, facturation, autre. Always pass it on a support reply: the workspace approval rules can depend on it, and the SAV report counts by type. |
| schedule | now | spread | "spread" (default for a batch of cold follow-ups): placed in the outbox, leave during business hours in Paris; "now": immediate (a reply to someone who wrote). |
Call this tool
Through the HTTP API, or from the MCP server with the run meta-tool.
curl https://api.ezyagents.fr/gateway/v1/run \
-H "Authorization: Bearer ezk_…" -H "Content-Type: application/json" \
-d '{"tool":"reply_email","input":{"replies":[],"emailId":"…","body":"…","replyAll":true}}'$
run({ "tool": "reply_email", "input": {"replies":[],"emailId":"…","body":"…","replyAll":true} })