template/create

When to Use

• Automated template provisioning: A multi-tenant SaaS onboarding workflow creates business-specific message templates (appointment reminders, order confirmations) as part of tenant setup, without requiring manual access to Meta Business Manager.
• Localisation at scale: A global campaign workflow creates copies of a base template in multiple languages (en_US, es_MX, fr_FR) by iterating through a language list and calling this node for each locale.
• Seasonal campaign preparation: A marketing operations workflow creates promotional templates ahead of campaign periods (Black Friday, year-end sales) and submits them weeks in advance to account for Meta's review window.
• Compliance-driven template management: A regulated industry workflow creates authentication templates with pre-approved OTP structures that meet Meta's AUTHENTICATION category requirements.
• Developer workflow integration: A CI/CD pipeline calls this node as part of deployment to create or update WhatsApp templates alongside application code changes.

Configuration

Connection

Operation

Components Structure

Each component object has a type field. Supported types:

• HEADER — Optional. Accepts format: TEXT, IMAGE, VIDEO, or DOCUMENT.
• BODY — Required. Contains the main message text. Supports variables in {{1}}, {{2}} format.
• FOOTER — Optional. Plain text footer, max 60 characters. Does not support variables.
• BUTTONS — Optional. Supports QUICK_REPLY (up to 3), URL (up to 2), and PHONE_NUMBER (up to 1).

Sample Configuration

{
  "resource": "template",
  "operation": "create",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "name": "order_shipped_notification",
  "language": "en_US",
  "category": "UTILITY",
  "components": "[{\"type\":\"HEADER\",\"format\":\"TEXT\",\"text\":\"Your Order Has Shipped\"},{\"type\":\"BODY\",\"text\":\"Hi {{1}}, your order #{{2}} has been shipped and will arrive by {{3}}. Track your delivery at: {{4}}\"},{\"type\":\"FOOTER\",\"text\":\"BizFirstAI Commerce\"},{\"type\":\"BUTTONS\",\"buttons\":[{\"type\":\"URL\",\"text\":\"Track Order\",\"url\":\"https://track.example.com/{{1}}\"}]}]"
}

Validation Errors

Output

Success Port

Fires after Meta accepts the template submission. The template is now in PENDING status and awaiting Meta review. Store the id to poll status later.

Error Port

Fires when Meta rejects the template or the submission fails.

Sample Output

{
  "id": "987654321098765",
  "templateStatus": "PENDING",
  "status": "created",
  "errorCode": null,
  "errorMessage": null,
  "rawResponse": "{\"id\":\"987654321098765\",\"status\":\"PENDING\"}"
}

Expression Reference

Node Policies & GuardRails

Examples

Create a UTILITY Order Confirmation Template

{
  "resource": "template",
  "operation": "create",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "name": "order_confirmation_v1",
  "language": "en_US",
  "category": "UTILITY",
  "components": "[{\"type\":\"BODY\",\"text\":\"Thank you for your order, {{1}}! Your order #{{2}} for {{3}} has been confirmed. Expected delivery: {{4}}.\"}]"
}

A new tenant onboarding workflow creates this standard order confirmation template as part of setup. After creation, a downstream node stores the returned id in the tenant settings table. A scheduled daily job polls template/get until status reaches APPROVED, then marks the template as ready in the configuration.

Create a MARKETING Template with Quick Reply Buttons

{
  "resource": "template",
  "operation": "create",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "name": "summer_sale_2024",
  "language": "en_US",
  "category": "MARKETING",
  "components": "[{\"type\":\"HEADER\",\"format\":\"IMAGE\",\"example\":{\"header_handle\":[\"{{ $input.bannerMediaHandle }}\"]}},{\"type\":\"BODY\",\"text\":\"Hi {{1}}, our Summer Sale starts tomorrow! Enjoy {{2}}% off everything. Shop now before stocks run out!\"},{\"type\":\"FOOTER\",\"text\":\"Reply STOP to unsubscribe\"},{\"type\":\"BUTTONS\",\"buttons\":[{\"type\":\"QUICK_REPLY\",\"text\":\"Shop Now\"},{\"type\":\"QUICK_REPLY\",\"text\":\"View Deals\"},{\"type\":\"QUICK_REPLY\",\"text\":\"Unsubscribe\"}]}]"
}

A campaign preparation workflow creates this template 2 weeks before the sale. The image header references a banner image already uploaded via media/upload. The template ID is stored and the workflow polls for approval daily until ready.

Create a Multi-Language Template Set

// Loop node iterates over: ["en_US", "es_MX", "fr_FR", "de_DE"]
{
  "resource": "template",
  "operation": "create",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "name": "appointment_reminder",
  "language": "{{ $loop.currentItem }}",
  "category": "UTILITY",
  "components": "{{ $input.componentsForLocale[$loop.currentItem] }}"
}

A localisation workflow creates the same template in 4 languages by looping through a language list. Each language's component JSON is stored in a componentsForLocale lookup object populated by a translation service upstream. All four template IDs are collected and stored for each locale's send pipeline.