StevoChat icon

StevoChat

Interact with StevoChat API

Actions12

Chat → Send Document

AI-generated

Overview

The node integrates with the StevoChat API to send various types of chat messages and perform session or webhook management. Specifically, for the Chat - Send Document operation, it allows sending a document file to a specified phone number via StevoChat. This is useful in scenarios where you want to automate sending files such as PDFs, Word documents, or other attachments directly through chat.

Practical examples include:

  • Sending invoices or contracts automatically to clients.
  • Delivering user manuals or guides after a support request.
  • Sharing reports or data exports in document format.

Properties

Name Meaning
Phone The recipient's phone number including country code.
Media URL The URL or base64 string of the document file to be sent.
Filename The name of the document file (e.g., "invoice.pdf"). Optional but helps identify the file.
ID (Optional) An optional message ID to track or reference the message.

Output

The output is a JSON array containing the response from the StevoChat API for each input item processed. Each element corresponds to the result of sending the document message, typically including metadata about the sent message such as status, message ID, timestamps, or error details if any occurred.

No binary data is output by this node; all responses are JSON objects representing the API's reply.

Dependencies

  • Requires an active StevoChat API key credential configured in n8n.
  • Network access to the StevoChat API endpoints.
  • Proper configuration of the node with valid phone numbers and accessible media URLs or base64 encoded files.

Troubleshooting

  • Invalid Phone Number: Ensure the phone number includes the correct country code and is formatted properly.
  • Media URL Issues: The media URL must be publicly accessible or a valid base64 string. If the file cannot be fetched, the API will return an error.
  • Filename Missing or Incorrect: While optional, providing a filename helps the recipient identify the document. Omitting it might cause confusion.
  • API Authentication Errors: Verify that the API key credential is correctly set up and has not expired.
  • Message ID Conflicts: If using the optional message ID, ensure it is unique per message to avoid conflicts.

Common error messages usually relate to invalid parameters or authentication failures. Checking the exact API response in the node output can help diagnose issues.

Links and References

Discussion