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 manage message templates and other communication resources. Specifically, for the Message Templates - Get Many operation, it retrieves multiple message templates from Yup.chat, optionally filtered or limited by user parameters.

Common scenarios where this node is beneficial include:

  • Fetching a list of available message templates to display or use in subsequent messaging workflows.
  • Automating template management by retrieving templates dynamically before sending templated messages.
  • Filtering templates based on creation date or other criteria to maintain an updated set of templates.

Example: A marketing automation workflow could use this node to get all WhatsApp message templates created after a certain date, then send promotional messages using those templates.

Properties

Name Meaning
Return All Whether to return all message templates or only up to a specified limit.
Limit Maximum number of message templates to return (used if "Return All" is false). Range: 1-500.
Filters Filter parameters as a string to narrow down results, e.g., filter=created_at:2023-01-01.

Output

The output is an array of JSON objects representing message templates retrieved from Yup.chat. Each item corresponds to one message template with its details as returned by the API.

The structure of each JSON object depends on the Yup.chat API response but typically includes fields such as template ID, name, body content, type (e.g., transactional or marketing), and parameters.

No binary data is output by this operation.

Dependencies

  • Requires an active Yup.chat API key credential configured in n8n.
  • The node makes HTTP requests to the Yup.chat API endpoint (default base URL: https://api.yup.chat).
  • Proper API permissions are needed to read message templates.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication errors.
    • Incorrect filter syntax may result in empty or error responses.
    • Requesting too many items without pagination or limits might lead to timeouts or rate limiting.

  • Error messages:

    • Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
    • HTTP 400 errors may indicate malformed filters or parameters; check filter syntax carefully.
    • Rate limit errors suggest too many requests in a short period; implement delays or reduce request frequency.

Links and References

Discussion