N8N Tools - Yup.chat icon

N8N Tools - Yup.chat

Send messages and manage communications through Yup.chat
Join our community

Actions17

Overview

This node integrates with the Yup.chat API to send SMS messages and manage communications. Specifically, for the SMS Messages - Send operation, it allows sending SMS messages either as plain text or using predefined message templates. This is useful in scenarios such as transactional notifications, marketing campaigns, or customer support where automated SMS communication is required.

Practical examples include:

  • Sending appointment reminders via SMS text.
  • Dispatching order confirmation messages using a template with dynamic fields.
  • Notifying customers about promotions or alerts through templated SMS.

Properties

Name Meaning
To Recipient phone number in E.164 format (e.g., "5511999999999").
From Sender identifier shown on the recipient's device; defaults to "Default" if not specified.
Message Type Type of message to send: Text (plain text message) or Template (predefined message).
Text The actual text content to send when Message Type is Text.
Template ID Identifier of the message template to use when Message Type is Template.
Template Fields Key-value pairs to fill placeholders in the selected template; multiple fields can be added.

Output

The node outputs an array of JSON objects representing the response from the Yup.chat API after sending the SMS message(s). Each output item corresponds to one message sent and contains details such as message status, IDs, timestamps, or error information if applicable.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Yup.chat API.
  • The base URL for the Yup.chat API is configurable but defaults to https://api.yup.chat.
  • Proper network access to the Yup.chat API endpoints is necessary.

Troubleshooting

  • Invalid Phone Number Format: Ensure the "To" property uses the correct E.164 format (e.g., country code + number without spaces).
  • Missing or Invalid API Key: Authentication errors occur if the API key credential is missing or incorrect. Verify credentials in n8n settings.
  • Template Errors: When using templates, ensure the Template ID exists and that all required template fields are provided with valid keys and values.
  • API Rate Limits or Network Issues: Temporary failures may happen due to rate limiting or connectivity problems. Retrying or checking network/firewall settings can help.
  • Error Messages: If the node returns an error object, check the message for clues such as invalid parameters or unauthorized access. Use the "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion