Actions126
- User Actions
- Group Actions
- Content Actions
- Post Actions
- Comment Actions
- Like Actions
- Activity Actions
- Notification Actions
- Space Actions
- Calendar Actions
- CFile Directory Actions
- CFile Actions
- CFile Item Management Actions
- Survey Actions
- Task Actions
- Task List Actions
- Wiki Page Actions
- Mail Conversation Actions
- Mail Entry Actions
- Mail Recipient Actions
- Session Actions
- File Actions
- Space Membership Actions
- Topic Actions
- Survey Answer Actions
- Survey Answers Actions
- Wiki Page Revision Actions
- Mail Tag Actions
Overview
This node interacts with the HumHub API to perform operations related to Mail Entries. Specifically, the 'Get' operation retrieves a specific mail entry by its message ID and entry ID. This is useful for scenarios where you need to fetch detailed information about a particular mail entry within a conversation, such as for email management or communication tracking within the HumHub platform.
Use Case Examples
- Retrieve a specific mail entry by providing the message ID and entry ID to get detailed information about that entry.
- Use the node to fetch mail entries for processing or analysis in workflows involving HumHub mail conversations.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use for the API request (Basic Auth or JWT Token). |
| MessageID | The ID of the mail conversation to which the entry belongs. |
| Entry ID | The ID of the specific mail entry to retrieve within the conversation. |
Output
JSON
id- The unique identifier of the mail entry.messageId- The ID of the mail conversation this entry belongs to.content- The content or body of the mail entry.createdAt- Timestamp when the mail entry was created.updatedAt- Timestamp when the mail entry was last updated.
Dependencies
- HumHub API
Troubleshooting
- Ensure that both 'MessageID' and 'Entry ID' are provided and valid numbers; missing or invalid IDs will cause the API request to fail.
- Authentication errors may occur if the provided credentials (Basic Auth or JWT Token) are incorrect or expired; verify credentials before running the node.
- API rate limits or network issues can cause request failures; check network connectivity and HumHub API status if errors persist.
