360 Dialog icon

360 Dialog

Consume 360 Dialog Whatsapp API
Join our community

Actions2

Overview

The 360 Dialog node for n8n allows you to interact with the 360 Dialog WhatsApp API. Specifically, when using the Template resource and the Get Templates operation, this node retrieves a list of WhatsApp message templates associated with your 360 Dialog account. You can optionally filter the results by template name.

Common scenarios:

  • Listing all available WhatsApp message templates for review or selection in automated workflows.
  • Filtering and retrieving details about a specific template by its name.
  • Integrating template management into broader automation processes (e.g., syncing templates with other systems).

Practical example:
You might use this node to fetch all templates before sending a templated WhatsApp message, ensuring you select a valid and up-to-date template.

Properties

Name Type Meaning
API Key String API key for authenticating requests to the 360 Dialog API.
Additional Fields Collection Optional fields for filtering results.
└ Template Name String If provided, filters the templates to return only the one with this name.

Output

  • The output is a JSON array containing one or more WhatsApp template objects.
  • Each object represents a template and includes properties such as name, namespace, language, and possibly other metadata defined by the 360 Dialog API.
  • If "Template Name" is specified and found, only that template's object is returned; if not found, an error is thrown.
  • If no filter is applied, all available templates are returned.

Example output:

[
  {
    "name": "order_confirmation",
    "namespace": "your_namespace",
    "language": "en",
    // ...other template properties
  }
]

Dependencies

  • External Service: Requires access to the 360 Dialog WhatsApp API.
  • API Key: You must provide a valid API key for authentication.
  • n8n Configuration: No special credentials configuration is required within n8n; the API key is supplied directly as a property.

Troubleshooting

Common issues:

  • Invalid or missing API Key: If the API key is incorrect or missing, the request will fail with an authentication error.
  • Template not found: If you specify a template name that does not exist, the node throws an error:
    Template "<name>" is not found!
    • Resolution: Double-check the template name for typos or ensure it exists in your 360 Dialog account.
  • Network/API errors: Issues with connectivity or the 360 Dialog API itself may result in generic error messages.

Error handling:

  • If "Continue On Fail" is enabled, errors are returned in the output as { "error": "<message>" } instead of stopping the workflow.

Links and References

Discussion