N8N Tools - Yup.chat icon

N8N Tools - Yup.chat

Send messages and manage communications through Yup.chat

Actions17

Overview

This node integrates with the Yup.chat API to manage message templates, specifically allowing users to create new message templates for WhatsApp. It is useful in scenarios where businesses want to automate and standardize their communication by defining reusable message templates with placeholders that can be dynamically filled when sending messages.

For example, a company can create a transactional template for order confirmations with placeholders like {{name}} and {{order_id}}. Later, this template can be used to send personalized messages to customers without rewriting the entire message each time.

Properties

Name Meaning
Name The name of the message template to create.
Body The content/body of the template including placeholders for dynamic parameters.
Type The type of the template. Options: "Transactional" or "Marketing".
Parameters JSON array of parameter names (placeholders) used in the template body, e.g., ["name", "order_id"].

Output

The output is a JSON object representing the created message template as returned by the Yup.chat API. This typically includes details such as the template ID, name, body, type, parameters, and other metadata provided by the API response.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Yup.chat API.
  • The base URL for the Yup.chat API defaults to https://api.yup.chat but can be configured via credentials.
  • The node uses HTTP requests to communicate with the Yup.chat REST API endpoints.

Troubleshooting

  • Invalid JSON in Parameters: If the "Parameters" field contains invalid JSON, the node will default to an empty array. Ensure the JSON array syntax is correct (e.g., ["name", "order_id"]).
  • API Authentication Errors: If the API key is missing or invalid, the node will fail with an authentication error. Verify that the API key credential is correctly set up.
  • Required Fields Missing: The "Name", "Body", and "Type" fields are required. Omitting any of these will cause the request to fail.
  • API Endpoint Issues: Network issues or incorrect base URL configuration may cause request failures. Confirm network connectivity and credential settings.

Links and References

Discussion