Skip to main content

Merge tag check

create_template and update_template apply the same merge tag check as campaign step templateData: a subject or body with a tag that is not in seamless://templates/variables is rejected with an “Unknown merge fields” error listing the tags. An AI prompt template (contentCategory: "ai_prompt") holds plain instructions that the AI runs for each contact, without merge tags, and skips that check. Merge tags from seamless://templates/variables sent in one anyway are saved as @ references to the contact’s fields, so its body can read back as HTML. Other tags stay as text. Access: Connect. See Access control.

list_templates

List email templates, or get a specific template by ID. When templateId is provided, returns that template with subject, body, and metadata. Otherwise returns a paginated table of templates. The seamless://templates resource provides a quick list without pagination. See seamless://templates/variables for available merge tag variables.

Arguments

integer | string
ID of a specific template to retrieve. Omit to list all.
string
Search templates by name (only used when listing).
string
Filter by template type. Omit to match every type.One of: email, call, linkedin-message, linkedin-connect-request, custom.
string
Opaque token from pagination.nextCursor
integer
Page size (default 15). Must match the first page’s when cursor is set
boolean
default:"false"
Include engagement statistics. Only used when listing.

Result

Returns a text content block and a structuredContent object with these fields. Treat every field as nullable: a value the record does not have comes back as null.
object[]
Result records when listingFields vary by record.
object
Pagination metadata when available. Carries only the values the service has, so treat a missing key as unknown rather than zero; nextCursor is null or absent on the last page.

create_template

Create a new email template with subject and body content. In static templates, use template variables like [first_name], [company], [title] for personalization — read seamless://templates/variables for all available merge tags. AI prompt templates (contentCategory “ai_prompt”) hold plain instructions with no merge tags. Returns the created template with its ID. Use list_email_footers to find footer IDs. 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

string
required
Name for the new template.
string
default:"email"
The type of template (default “email”).One of: email, call, linkedin-message, linkedin-connect-request, custom.
string
Content category: “static” for standard templates with merge tags, “ai_prompt” for a prompt the AI runs per contact (plain instructions, no merge tags or variables in the body).One of: static, ai_prompt.
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
Static templates: 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. AI prompts (contentCategory “ai_prompt”): PLAIN TEXT instructions the AI runs for each contact. Do NOT include merge tags or variables (e.g. [first_name], [company]); say “address them by first name”, not a tag.
ID of an email footer to attach.
integer | string
ID of an email signature to attach.

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.

Example

update_template

Update an existing email template name, subject, or body. In static templates, use template variables like [first_name], [company] for personalization (see seamless://templates/variables); AI prompt templates (contentCategory “ai_prompt”) hold plain instructions with no merge tags. Returns the updated template. 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 ID of the template to update.
string
Only needed to change the template type. Omit to keep the existing type.One of: email, call, linkedin-message, linkedin-connect-request, custom.
string
Content category: “static” for standard templates with merge tags, “ai_prompt” for a prompt the AI runs per contact (plain instructions, no merge tags or variables in the body).One of: static, ai_prompt.
string
Updated template name.
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
Static templates: 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. AI prompts (contentCategory “ai_prompt”): PLAIN TEXT instructions the AI runs for each contact. Do NOT include merge tags or variables (e.g. [first_name], [company]); say “address them by first name”, not a tag.

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.

delete_template

Permanently delete an email template by its ID. This cannot be undone. Use list_templates to find template IDs.
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 ID of the template to delete.
string
Restricts the delete to templates of this type. Omit to match every type.One of: email, call, linkedin-message, linkedin-connect-request, custom.

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.