Create WhatApp Template

Create a WhatsApp template

Options

Body
Values to create a WhatsApp template

Request body which must comply to the following JSON Schema:

{
  "required" : [ "bodyText", "category", "language", "name" ],
  "type" : "object",
  "properties" : {
    "name" : {
      "type" : "string",
      "description" : "Name of the template",
      "example" : "Test template"
    },
    "language" : {
      "type" : "string",
      "description" : "Language of the template. For Example :\n**en** for English\n",
      "example" : "en"
    },
    "category" : {
      "type" : "string",
      "description" : "Category of the template",
      "example" : "MARKETING",
      "enum" : [ "MARKETING", "UTILITY" ]
    },
    "mediaUrl" : {
      "type" : "string",
      "description" : "Absolute url of the media file **(no local file)** for the header. **Use this field in you want to add media in Template header and headerText is empty**.\nAllowed extensions for media files are:\n#### jpeg | png | mp4 | pdf\n",
      "example" : "https://attachment.domain.com"
    },
    "bodyText" : {
      "type" : "string",
      "description" : "Body of the template. **Maximum allowed characters are 1024**",
      "example" : "making it look like readable English"
    },
    "headerText" : {
      "type" : "string",
      "description" : "Text content of the header in the template. **Maximum allowed characters are 45**\n**Use this field to add text content in template header and if mediaUrl is empty**\n",
      "example" : "Test WhatsApp campaign"
    },
    "source" : {
      "type" : "string",
      "description" : "source of the template",
      "enum" : [ "Automation", "Conversations" ]
    }
  }
}
Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.