Skip to main content
Access: Connect. See Access control.

create_email_draft

Create an email draft for a contact. The draft is saved but not sent until you call send_email_draft. Returns the draft with its ID. Use list_email_accounts or seamless://email-accounts to find valid sender addresses. Use template variables like [first_name], [company] for personalization (see seamless://templates/variables). EMAIL AUTHORING RULES:
  • PLAIN TEXT ONLY. Never emit HTML tags such as <p>, </p>, <br>, <br/>, <div>, <a>, <span>. Never wrap paragraphs in tags. Never close with </p>. If you find yourself typing ”<”, stop and use a newline instead.
  • NO sign-off line of any kind. Forbidden: “Best,”, “Thanks,”, “Regards,”, “Cheers,”, “Sincerely,”, followed by a name or anything else. The platform appends signatures automatically.
  • NO invented placeholders. Forbidden examples: [pain_point], [value_prop], [Your Name], [First Name] — any token that is not on the available variable list. Saving a template or campaign step with an unknown tag fails with an error that lists the tags. Emails and drafts are not checked: unknown tags pass through unresolved and the recipient sees the literal text. Use ONLY square-bracket merge tags from seamless://templates/variables (e.g. [first_name], [company], [title]), or real values, or rewrite the sentence to omit the missing detail.
  • Use exactly ONE blank line between sentences. A blank line is one empty line — never two or more.
Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: “Hey Sarah,” or “Hi David,” Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don’t know. seamless://me describes the sender: the authenticated user, their About Me context, and their organization. Use it to accurately represent the sender. Never apply the sender’s name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don’t disclose that the information is missing in the output. Just omit it.

Arguments

integer | string
required
The saved contact ID to email (from get_my_contacts, not search results).
string
required
Sender email address. Must be a connected email account (use list_email_accounts).
string
required
Recipient email address.
string
PLAIN TEXT subject line, under 45 characters, specific (not clickbait). NO HTML. Supports square-bracket merge tags like [first_name], [company] from seamless://templates/variables. Required if no templateId.
string
PLAIN TEXT ONLY. NO HTML tags whatsoever (no <p>, </p>, <br>, <div>, <a>, <span>). NO markdown. NO sign-off line (“Best,”, “Thanks,”, “Regards,” etc. — appended automatically). NO invented placeholders (e.g. [pain_point], [value_prop], [Your Name], [First Name] — any token not on the variable list); a template or campaign step with an unknown tag is rejected, and in emails and drafts it passes through unresolved and the recipient sees the literal text. Use ONLY [first_name], [company], [title] square-bracket merge tags from seamless://templates/variables, or real values. Use exactly ONE blank line between sentences (single empty line — never stack multiple). See tool description for full authoring rules. Required if no templateId.
string
CC email addresses.
string
BCC email addresses.
integer | string
Template ID to use (provides subject/body if not specified).
string
Schedule send time in ISO 8601 format.

Result

Returns a text content block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.

get_email_draft

Retrieve a previously created email draft by its ID. Returns the draft content and metadata.

Arguments

integer | string
required
The email draft ID (corresponds to the task ID returned when creating a draft).

Result

Returns a text content block and a structuredContent object. Its fields are the record’s own and vary by record; treat every field as nullable.

update_email_draft

Update the content of an existing email draft before sending. Returns the updated draft. EMAIL AUTHORING RULES:
  • PLAIN TEXT ONLY. Never emit HTML tags such as <p>, </p>, <br>, <br/>, <div>, <a>, <span>. Never wrap paragraphs in tags. Never close with </p>. If you find yourself typing ”<”, stop and use a newline instead.
  • NO sign-off line of any kind. Forbidden: “Best,”, “Thanks,”, “Regards,”, “Cheers,”, “Sincerely,”, followed by a name or anything else. The platform appends signatures automatically.
  • NO invented placeholders. Forbidden examples: [pain_point], [value_prop], [Your Name], [First Name] — any token that is not on the available variable list. Saving a template or campaign step with an unknown tag fails with an error that lists the tags. Emails and drafts are not checked: unknown tags pass through unresolved and the recipient sees the literal text. Use ONLY square-bracket merge tags from seamless://templates/variables (e.g. [first_name], [company], [title]), or real values, or rewrite the sentence to omit the missing detail.
  • Use exactly ONE blank line between sentences. A blank line is one empty line — never two or more.
Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: “Hey Sarah,” or “Hi David,” Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don’t know. seamless://me describes the sender: the authenticated user, their About Me context, and their organization. Use it to accurately represent the sender. Never apply the sender’s name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don’t disclose that the information is missing in the output. Just omit it.
May overwrite, remove, or send data in a way that cannot be undone. Ask for explicit confirmation before calling this tool in an agent workflow.

Arguments

integer | string
required
The email draft ID to update.
string
PLAIN TEXT subject line, under 45 characters, specific (not clickbait). NO HTML. Supports square-bracket merge tags like [first_name], [company] from seamless://templates/variables.
string
PLAIN TEXT ONLY. NO HTML tags whatsoever (no <p>, </p>, <br>, <div>, <a>, <span>). NO markdown. NO sign-off line (“Best,”, “Thanks,”, “Regards,” etc. — appended automatically). NO invented placeholders (e.g. [pain_point], [value_prop], [Your Name], [First Name] — any token not on the variable list); a template or campaign step with an unknown tag is rejected, and in emails and drafts it passes through unresolved and the recipient sees the literal text. Use ONLY [first_name], [company], [title] square-bracket merge tags from seamless://templates/variables, or real values. Use exactly ONE blank line between sentences (single empty line — never stack multiple). See tool description for full authoring rules.
string
Updated recipient email address.
string
Updated CC email addresses.
string
Updated BCC email addresses.
string
Schedule send time in ISO 8601 format.

Result

Returns a text content block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.

send_email_draft

Send a previously created email draft. The email will be sent immediately. If a send limit was reached or the provider failed temporarily, the email is queued instead: status is SCHEDULED or RETRYING and it will send on its own, so do not send it again. Does not consume search/research credits. Use create_email_draft first to create the draft.
May overwrite, remove, or send data in a way that cannot be undone. Ask for explicit confirmation before calling this tool in an agent workflow.

Arguments

integer | string
required
The email draft ID to send.
string
Sender email address (optional, uses draft default if not provided).

Result

Returns a text content block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.

send_email

Send an email directly to a contact in one step (creates and sends immediately). If a send limit was reached or the provider failed temporarily, the email is queued instead: status is SCHEDULED or RETRYING and it will send on its own, so do not send it again. Does not consume search/research credits. Use template variables like [first_name], [company] for personalization (see seamless://templates/variables). For more control, use create_email_draft + send_email_draft instead. EMAIL AUTHORING RULES:
  • PLAIN TEXT ONLY. Never emit HTML tags such as <p>, </p>, <br>, <br/>, <div>, <a>, <span>. Never wrap paragraphs in tags. Never close with </p>. If you find yourself typing ”<”, stop and use a newline instead.
  • NO sign-off line of any kind. Forbidden: “Best,”, “Thanks,”, “Regards,”, “Cheers,”, “Sincerely,”, followed by a name or anything else. The platform appends signatures automatically.
  • NO invented placeholders. Forbidden examples: [pain_point], [value_prop], [Your Name], [First Name] — any token that is not on the available variable list. Saving a template or campaign step with an unknown tag fails with an error that lists the tags. Emails and drafts are not checked: unknown tags pass through unresolved and the recipient sees the literal text. Use ONLY square-bracket merge tags from seamless://templates/variables (e.g. [first_name], [company], [title]), or real values, or rewrite the sentence to omit the missing detail.
  • Use exactly ONE blank line between sentences. A blank line is one empty line — never two or more.
Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: “Hey Sarah,” or “Hi David,” Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don’t know. seamless://me describes the sender: the authenticated user, their About Me context, and their organization. Use it to accurately represent the sender. Never apply the sender’s name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don’t disclose that the information is missing in the output. Just omit it.
May overwrite, remove, or send data in a way that cannot be undone. Ask for explicit confirmation before calling this tool in an agent workflow.

Arguments

integer | string
required
The saved contact ID to email (from get_my_contacts, not search results).
string
required
Sender email address. Must be a connected email account (use list_email_accounts).
string
required
Recipient email address.
string
PLAIN TEXT subject line, under 45 characters, specific (not clickbait). NO HTML. Supports square-bracket merge tags like [first_name], [company] from seamless://templates/variables. Required if no templateId.
string
PLAIN TEXT ONLY. NO HTML tags whatsoever (no <p>, </p>, <br>, <div>, <a>, <span>). NO markdown. NO sign-off line (“Best,”, “Thanks,”, “Regards,” etc. — appended automatically). NO invented placeholders (e.g. [pain_point], [value_prop], [Your Name], [First Name] — any token not on the variable list); a template or campaign step with an unknown tag is rejected, and in emails and drafts it passes through unresolved and the recipient sees the literal text. Use ONLY [first_name], [company], [title] square-bracket merge tags from seamless://templates/variables, or real values. Use exactly ONE blank line between sentences (single empty line — never stack multiple). See tool description for full authoring rules. Required if no templateId.
string
CC email addresses.
string
BCC email addresses.
integer | string
Template ID to use.

Result

Returns a text content block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
Sends to recipients on the public internet. Require explicit user approval in agent workflows.

Example

send_bulk_email

Send emails to multiple contacts matching filter criteria. filters must include at least one of lists, contactIds, campaignIds, or a text query — an empty filter set is rejected so the whole book is never mailed. Resolves the audience first and rejects the request if more than 500 contacts match — the send is not truncated. Opted-out and unsubscribed contacts are skipped. Does not consume public API credits. Pass idempotencyKey so a retry of the same request returns the original job. Reusing a key with a different audience or message is rejected. Use template variables like [first_name], [company] for personalization (see seamless://templates/variables). Returns jobId plus matched, queued, and skipped counts. EMAIL AUTHORING RULES:
  • PLAIN TEXT ONLY. Never emit HTML tags such as <p>, </p>, <br>, <br/>, <div>, <a>, <span>. Never wrap paragraphs in tags. Never close with </p>. If you find yourself typing ”<”, stop and use a newline instead.
  • NO sign-off line of any kind. Forbidden: “Best,”, “Thanks,”, “Regards,”, “Cheers,”, “Sincerely,”, followed by a name or anything else. The platform appends signatures automatically.
  • NO invented placeholders. Forbidden examples: [pain_point], [value_prop], [Your Name], [First Name] — any token that is not on the available variable list. Saving a template or campaign step with an unknown tag fails with an error that lists the tags. Emails and drafts are not checked: unknown tags pass through unresolved and the recipient sees the literal text. Use ONLY square-bracket merge tags from seamless://templates/variables (e.g. [first_name], [company], [title]), or real values, or rewrite the sentence to omit the missing detail.
  • Use exactly ONE blank line between sentences. A blank line is one empty line — never two or more.
Plain text only. No HTML, markdown, quotes, code blocks, sign-offs, or signatures. If not specified, keep word count under 125 words. Open with name + comma: “Hey Sarah,” or “Hi David,” Blank line between every sentence. No exceptions. If not specified, keep subject line under 45 characters. Specific, not clickbait. Tone: If not specified, keep the tone as confident, direct, conversational. Vary sentence length. Avoid em dashes entirely when possible, max one per email. No filler openers. No vague closers. Never fabricate stats or details. Never invent recipient info. Never invent variables like [Your Name] for things you don’t know. seamless://me describes the sender: the authenticated user, their About Me context, and their organization. Use it to accurately represent the sender. Never apply the sender’s name, title, company, or details to the recipient. If a request cannot be completed due to lack of data, don’t disclose that the information is missing in the output. Just omit it.
May overwrite, remove, or send data in a way that cannot be undone. Ask for explicit confirmation before calling this tool in an agent workflow.

Arguments

string
required
Sender email address. Must be a connected email account (use list_email_accounts).
string
PLAIN TEXT subject line, under 45 characters, specific (not clickbait). NO HTML. Supports square-bracket merge tags like [first_name], [company] from seamless://templates/variables. Required if no templateId.
string
PLAIN TEXT ONLY. NO HTML tags whatsoever (no <p>, </p>, <br>, <div>, <a>, <span>). NO markdown. NO sign-off line (“Best,”, “Thanks,”, “Regards,” etc. — appended automatically). NO invented placeholders (e.g. [pain_point], [value_prop], [Your Name], [First Name] — any token not on the variable list); a template or campaign step with an unknown tag is rejected, and in emails and drafts it passes through unresolved and the recipient sees the literal text. Use ONLY [first_name], [company], [title] square-bracket merge tags from seamless://templates/variables, or real values. Use exactly ONE blank line between sentences (single empty line — never stack multiple). See tool description for full authoring rules. Required if no templateId.
integer | string
Template ID to use. Templates support merge tag variables for personalization.
object
required
Filter criteria to select saved contacts for bulk email. Must include at least one of lists, contactIds, campaignIds, or a text query. Unknown keys are rejected. At most 500 contacts may match.
string
Schedule send time in ISO 8601 format.
string
Retry token. Same key plus the same request returns the original job. Same key plus a different audience or message is rejected.

Result

Returns a text content block describing the outcome, plus a structuredContent object that mirrors it. This tool publishes no outputSchema, so the object’s fields are not guaranteed; treat every field as optional and nullable.
Sends to many recipients at once. Require explicit user approval and show the audience size before calling.

Example