EitaaMessenger

Interact with Eitaa Messenger API

Actions3

Chat Actions

Overview

The EitaaMessenger node for n8n allows you to interact with the Eitaa Messenger API. Specifically, when using the Chat resource and the Get Channel History operation, this node retrieves the message history from a specified chat channel. This is useful for automating workflows that need to analyze, archive, or process messages from Eitaa channels.

Practical examples:

Archiving all messages from a specific Eitaa channel into a database.
Triggering notifications or further automation based on new messages in a channel.
Performing sentiment analysis or content moderation on channel history.

Properties

Name	Meaning
Chat ID	Unique identifier for the target chat. Required to specify which channel's history to fetch.

Output

The output consists of an array of objects, each representing a user associated with the channel history. Each object is returned in the json field. The exact structure of each object depends on the Eitaa API response for channel history users, but typically includes user details such as IDs, usernames, and other metadata.

Example output:

[
  {
    "json": {
      // User data fields as returned by Eitaa API
    },
    "pairedItem": {
      "item": 0
    }
  },
  ...
]

Note: The node does not output binary data.

Dependencies

External Service: Requires access to the Eitaa Messenger API.
API Key/Credentials: You must configure the eitaaMessengerApi credential in n8n, which should include a valid API token.
n8n Configuration: Ensure the credentials are set up in your n8n instance under the appropriate name.

Troubleshooting

Common issues:

Invalid or missing Chat ID: If the provided Chat ID is incorrect or empty, the node will fail to retrieve channel history.
Authentication errors: If the API token is invalid or expired, authentication will fail. Refresh or update your credentials.
Insufficient permissions: The account used may lack permission to access the specified channel's history.

Error messages and resolutions:

"Invalid chatId" – Double-check the Chat ID value.
"Authentication failed" – Verify your API token in the credentials.
"No history found" – Ensure the channel exists and contains messages.