Skip to content

Zoho: Send mail merge email

Zoho mailMerge.postSendMailMerge: arguments, response, policy and SDK examples.

← Mail merge operations · Get started

Operation zoho.postsendmailmerge

Provider route: POST /crm/v8/{moduleApiName}/{recordId}/actions/send_mail_merge. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/zoho with npm, or alter-sdk-zoho with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { ZohoIntegration } from "@alter-ai/zoho";
async function execute(input: Parameters<ZohoIntegration["mailMerge"]["postSendMailMerge"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new ZohoIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.mailMerge.postSendMailMerge(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_zoho import ZohoIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = ZohoIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.mail_merge.post_send_mail_merge(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.moduleApiNamestringRequired within parentMaximum length: 255
path.recordIdintegerRequired within parentFormat: int64
bodyModelOptionalExpand Send mail merge email — request body — body

Referenced models: Send mail merge email — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Send mail merge email — response body

Referenced models: Send mail merge email — response body

Send mail merge email — response body
FieldTypePresenceDescription and constraints
$objectRootRepresents the response body returned upon successful initiation of the send mail merge operation.
Additional keys: not allowed
send_mail_mergearrayOptionalRepresents the list of send mail merge response objects.
Maximum items: 1
send_mail_merge[]ModelEach itemExpand Send mail merge email — response body — send mail merge item

Referenced models: Send mail merge email — response body — send mail merge item

Send mail merge email — request body — body
FieldTypePresenceDescription and constraints
$objectRootRepresents the request body schema for the send mail merge operation.
Additional keys: not allowed
send_mail_mergearrayRequired within parentRepresents the list of send mail merge request objects. Contains one object per request.
Maximum items: 1
send_mail_merge[]ModelEach itemExpand Send mail merge email — request body — body send mail merge item

Referenced models: Send mail merge email — request body — body send mail merge item

Send mail merge email — response body — send mail merge item
FieldTypePresenceDescription and constraints
$objectRootRepresents the response payload for a send mail merge operation.
Additional keys: not allowed
codestringOptionalRepresents the response code indicating the result of the send mail merge operation.
Maximum length: 255
detailsModelOptionalExpand Send mail merge email — response body — send mail merge item details
messagestringOptionalRepresents the message describing the result of the send mail merge operation.
Maximum length: 255
statusstringOptionalRepresents the status of the send mail merge operation.
Possible values:
**success** - The mail merge email was initiated successfully.
**error** - The mail merge email failed to initiate.

Known values: success, error
Maximum length: 255

Referenced models: Send mail merge email — response body — send mail merge item details

Send mail merge email — request body — body send mail merge item
FieldTypePresenceDescription and constraints
$objectRootRepresents the request payload for a send mail merge operation, including the template, recipient addresses, subject, message body, and optional attachment settings.
Additional keys: not allowed
attachment_namestringOptionalRepresents the name of the attachment to include in the mail merge email.
Maximum length: 255
bcc_emailarrayOptionalRepresents the list of email addresses to include in the BCC field of the mail merge email.
Maximum items: 1
bcc_email[]ModelEach itemExpand Send mail merge email — request body — body send mail merge item bcc email item
cc_emailarrayOptionalRepresents the list of email addresses to include in the CC field of the mail merge email.
Maximum items: 1
cc_email[]ModelEach itemExpand Send mail merge email — request body — body send mail merge item cc email item
from_addressModelOptionalExpand Send mail merge email — request body — body send mail merge item from address
The email ID you want to use to send emails from. This email address must be the one of the org-verified email addresses or the current user's email ID.
mail_merge_templateModelRequired within parentExpand Send mail merge email — request body — body send mail merge item mail merge template
Mailmerge Object to pass Template details (Required)
messagestringOptionalRepresents the body or content of the email you want to send. It can include up to **100,000 characters**.


Maximum length: 100000
subjectstringOptionalRepresents the subject line of the mail merge email.
Maximum length: 255
to_addressarrayOptionalRepresents the list of email addresses to send the mail merge email to.
Maximum items: 2
to_address[]ModelEach itemExpand Send mail merge email — request body — body send mail merge item to address item
typestringOptionalRepresents the attachment type for the mail merge email.
Possible values:
**inline** - Includes the mail merge document as an inline image in the email.
**attachment** - Attaches the mail merge document as a separate file in the email.

One of: inline, attachment
Maximum length: 10

Referenced models: Send mail merge email — request body — body send mail merge item bcc email item, Send mail merge email — request body — body send mail merge item cc email item, Send mail merge email — request body — body send mail merge item from address, Send mail merge email — request body — body send mail merge item mail merge template, Send mail merge email — request body — body send mail merge item to address item

Send mail merge email — response body — send mail merge item details
FieldTypePresenceDescription and constraints
$objectRootRepresents the response details returned upon successful initiation of the send mail merge operation.
Additional keys: not allowed
report_linkstringOptionalRepresents the URL of the mail merge job report.
Format: uri
Maximum length: 255
Send mail merge email — request body — body send mail merge item bcc email item
FieldTypePresenceDescription and constraints
$objectRootRepresents a BCC recipient entry for a mail merge email, containing the address type and email value.
Additional keys: not allowed
typestringRequired within parentRepresents the type of the address.
Possible values:
**email** - Indicates that the value is an email address.

One of: email
Maximum length: 5
valuestringRequired within parentRepresents the email address to include in the BCC list for the mail merge email.
Format: email
Maximum length: 255
Pattern: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$
Send mail merge email — request body — body send mail merge item cc email item
FieldTypePresenceDescription and constraints
$objectRootRepresents a CC recipient entry for a mail merge email, containing the address type and email value.
Additional keys: not allowed
typestringRequired within parentRepresents the type of the address.
Possible values:
**email** - Indicates that the value is an email address.

One of: email
Maximum length: 5
valuestringRequired within parentRepresents the email address to include in the CC list for the mail merge email.
Format: email
Maximum length: 255
Pattern: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$
Send mail merge email — request body — body send mail merge item from address
FieldTypePresenceDescription and constraints
$objectRootRepresents the sender address for a mail merge email, containing the address type and an org-verified or current user's email address.
Additional keys: not allowed
typestringRequired within parentRepresents the type of the address.
Possible values:
**email** - Indicates the value is an email address.

One of: email
Maximum length: 5
valuestringRequired within parentRepresents the sender email address used to send the mail merge email.
Format: email
Maximum length: 255
Pattern: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$
Send mail merge email — request body — body send mail merge item mail merge template
FieldTypePresenceDescription and constraints
$objectRootRepresents the mail merge template reference, identified by the template name.
Additional keys: not allowed
namestringRequired within parentRepresents the name of the mail merge template to use for the operation.
Maximum length: 255
Send mail merge email — request body — body send mail merge item to address item
FieldTypePresenceDescription and constraints
$objectRootRepresents a recipient address entry for a mail merge email, containing the address type and email value.
Additional keys: not allowed
typestringRequired within parentRepresents the type of the address.
Possible values:
**email** - Indicates the value is an email address.

One of: email
Maximum length: 5
valuestringRequired within parentRepresents the recipient email address for the mail merge email.
Format: email
Maximum length: 255
Pattern: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$

SDK function policy ID: zoho.postsendmailmerge. Catalog operation: postSendMailMerge. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.