ZAPIN icon

ZAPIN

Interact with Zapin EVO

Message → Send Status

AI-generated

Overview

This node operation allows sending a status update through the Messages API. It supports posting different types of statuses such as text, image, video, or audio. Users can specify the instance name sending the status, the content or URL of the media, optional captions for image or video statuses, background color, font style for text, and whether to send the status to all contacts or a specific list of contacts.

Use Case Examples

  1. Sending a text status update to all contacts with a custom background color and font.
  2. Posting an image status with a caption to a selected list of contacts.
  3. Sharing a video or audio status by providing the media URL and optional caption.

Properties

Name Meaning
Instance Name The name of the instance that will send the status, required to identify the sender.
Status Type The type of status to post, such as text, image, video, or audio.
Content Or URL The content for text status or the URL of the image, video, or audio to be posted, required for the status content.
Text For Image/Video Status Optional text caption to accompany image or video statuses.
Background Color Background color for the status text, specified as a color code.
Font Of Text Font style for the text in the status, with several predefined font options.
Send To All Boolean flag indicating whether to send the status to all contacts.
Contact List Comma-separated list of contacts who will receive the status, required if not sending to all contacts.

Output

JSON

  • statusId - Identifier of the sent status message.
  • statusType - Type of the status sent (text, image, video, audio).
  • sentToAll - Boolean indicating if the status was sent to all contacts.
  • recipients - List of contacts who received the status.
  • timestamp - Timestamp when the status was sent.

Dependencies

  • An API key credential for authenticating with the Messages API

Troubleshooting

  • Ensure the 'Instance Name' is correctly specified and matches the sender instance in the system.
  • If sending to specific contacts, verify the 'Contact List' is correctly formatted as a comma-separated string and contains valid contact identifiers.
  • Check that the 'Content Or URL' field is correctly filled with valid text or media URL depending on the status type.
  • If the node throws an 'Unsupported operation' error, verify that the resource and operation names are correctly set to 'Message' and 'Send Status' respectively.

Discussion