Actions13
- Chats Actions
- Companies Actions
- Email Campaign Trackers Actions
- Files Actions
- Sales Actions
Overview
The node interacts with the MagicDoor API, specifically allowing users to retrieve chat messages by their message ID. This operation is useful when you want to fetch details of a specific chat message from the MagicDoor service, for example, to display message content, analyze conversations, or integrate chat data into other workflows.
Properties
| Name | Meaning |
|---|---|
| Message ID | The ID of the message to retrieve |
Output
The output will contain JSON data representing the details of the requested chat message. This typically includes message content, sender information, timestamps, and any metadata provided by the MagicDoor API related to that message. The node does not explicitly mention binary data output, so it is assumed to be JSON only.
Dependencies
- Requires an API key credential for authenticating with the MagicDoor API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the MagicDoor API endpoints defined externally (in
MagicDoorEndpoints).
Troubleshooting
- Common issues:
- Invalid or missing Message ID: Ensure the Message ID is provided and is a valid number.
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Network or API endpoint errors: Check the base URL configuration and network connectivity.
- Error messages:
- HTTP status errors are ignored by default (
ignoreHttpStatusErrors: true), so errors might need to be handled downstream or checked manually. - If no message is found for the given ID, the API may return an empty response or error; verify the ID correctness.
- HTTP status errors are ignored by default (
Links and References
- Refer to the MagicDoor API documentation for detailed information about chat message retrieval endpoints and response formats.