Actions3
Overview
The EitaaMessenger node for n8n allows you to interact with the Eitaa Messenger API. Specifically, when using the "Chat" resource and the "Resolve Username" operation, this node resolves a given username (for either a user or a channel) to its corresponding details on Eitaa Messenger. This is useful in scenarios where you need to fetch information about a user or channel based on their username, such as automating user lookups, verifying usernames, or integrating Eitaa data into other workflows.
Example use cases:
- Verifying if a username exists before sending a message.
- Fetching user/channel details for logging or enrichment in CRM systems.
- Automating onboarding processes by resolving usernames to IDs.
Properties
| Name | Meaning |
|---|---|
| Username | Username of the channel or the user. Example: mtp1376. Required for this operation. |
Output
The output will be a JSON object containing the resolved details of the specified username. The exact structure depends on the Eitaa API response, but typically includes fields such as user or channel ID, name, and other metadata associated with the username.
Example output:
{
"id": 123456789,
"username": "mtp1376",
"type": "user",
"first_name": "John",
"last_name": "Doe"
}
Note: Actual fields may vary depending on the Eitaa API.
Dependencies
- External Service: Requires access to the Eitaa Messenger API.
- API Key/Credentials: You must configure the
eitaaMessengerApicredentials in n8n, which should include a valid API token.
Troubleshooting
- Invalid Username: If the provided username does not exist, the node may return an error or an empty result. Double-check the spelling and existence of the username.
- Authentication Errors: If your API token is invalid or expired, you may receive authentication errors. Ensure your credentials are up-to-date in n8n.
- Network Issues: Connectivity problems between n8n and the Eitaa API can cause failures. Check your network connection and any firewall settings.