uChat

Integração com a API do uChat

Fluxo → Enviar Para Contato

AI-generated

Overview

This node integrates with the uChat API to perform various operations related to messaging and contact management. Specifically, the 'Enviar Para Contato' operation under the 'Fluxo' resource sends a predefined flow (sub-flow) to a specified contact identified by a unique user identifier (user_ns). This is useful for automating communication workflows, such as sending targeted messages or sequences to individual contacts based on their unique identifiers.

Use Case Examples

  1. Sending a marketing or support flow to a specific contact by their unique user_ns.
  2. Triggering a customer onboarding flow for a new subscriber automatically.

Properties

Name Meaning
User NS Unique identifier of the contact (user_ns) to whom the flow will be sent.
Nome Ou ID Do Fluxo Name or ID The name or ID of the flow (sub-flow) to send to the contact. Can be selected from a list or specified using an expression.

Output

JSON

  • user_ns - The unique identifier of the contact to whom the flow was sent.
  • sub_flow_ns - The identifier of the flow (sub-flow) that was sent to the contact.
  • status - The status or result of the API call indicating success or failure of sending the flow.

Dependencies

  • Requires an API key credential for authenticating with the uChat API.

Troubleshooting

  • Ensure the 'userNs' parameter is correctly set to a valid contact identifier; otherwise, the API call will fail.
  • Verify that the 'flowName' corresponds to an existing flow or sub-flow in the uChat system; invalid flow IDs will cause errors.
  • Check API authentication credentials if requests fail due to authorization errors.
  • If the node throws JSON parsing errors, ensure that any expressions used for 'flowName' are correctly formatted.

Links

  • n8n Expressions - Documentation on how to use expressions in n8n to dynamically set parameters like flowName.
  • uChat API Documentation - Official API documentation for uChat, detailing endpoints and usage.

Discussion