Avito Get Messages icon

Avito Get Messages

Join our community

Overview

This node, named "Avito Get Messages," is designed to retrieve messages from a messaging service associated with Avito. It fetches messages for a specific user and chat by using an authentication token. This node is useful in scenarios where you want to automate the retrieval of chat messages for processing, monitoring, or integration with other workflows.

For example, you might use this node to:

  • Automatically pull new messages from a user's chat on Avito for analysis or archiving.
  • Integrate chat data into a CRM or customer support system.
  • Trigger further actions based on incoming messages.

Properties

Name Meaning
User id The identifier of the user whose messages you want to retrieve.
Chat id The identifier of the chat conversation from which to get messages.
Token The authentication token required to authorize access to the messaging API.

Output

The node outputs a JSON array containing an object with a messages field. This field holds the list of messages retrieved from the specified chat. The structure looks like:

[
  {
    "messages": [ /* array of message objects */ ]
  }
]

Each message object represents an individual message from the chat. The exact structure of each message depends on the external API response but typically includes details such as sender, content, timestamp, etc.

The node does not output any binary data.

Dependencies

  • Requires access to an external messaging API (referred to here as AvitoApi).
  • Needs a valid authentication token to be provided via the token property.
  • No additional n8n-specific credentials are referenced; the token must be supplied directly.

Troubleshooting

  • Missing or invalid token: If the token is missing or incorrect, the API call will fail. Ensure the token is valid and has the necessary permissions.
  • Incorrect userId or chatId: Providing wrong identifiers may result in empty message lists or errors. Verify these IDs correspond to existing users and chats.
  • API connectivity issues: Network problems or API downtime can cause failures. Check network status and API availability.
  • Unexpected API response: If the API changes its response format, the node might not parse messages correctly. Update the node or handle new formats accordingly.

Links and References

Discussion