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 operation creates a new mail conversation in the HumHub platform. It is useful for initiating email threads or discussions by specifying a conversation title, the first message content, and the recipients. For example, it can be used to automate sending notifications or starting collaborative discussions among users identified by their GUIDs.
Use Case Examples
- Create a mail conversation with title 'Project Update', message 'Please find the latest project updates attached.', and recipients '8eddbecb-8207-4848-bba6-5910115d3e4a,b6b66077-916d-4718-af28-5ffc2089530'.
- Start a new mail conversation to notify team members about a meeting schedule.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use for the API request, either Basic Auth or JWT Token. |
| Title | The title of the mail conversation to be created. |
| Message | The content of the first message entry in the mail conversation. |
| Recipients | Comma-separated GUIDs of users who will be recipients of the mail conversation. |
Output
JSON
title- The title of the created mail conversation.message- The content of the first message entry in the conversation.recipient- Array of recipient user GUIDs included in the conversation.id- Unique identifier of the created mail conversation.
Dependencies
- HumHub API
Troubleshooting
- Ensure that the recipient GUIDs are correctly formatted and separated by commas; otherwise, the API request may fail.
- The node requires valid authentication credentials (Basic Auth or JWT Token) configured in n8n; missing or incorrect credentials will cause authentication errors.
- If the title or message fields are empty, the API will reject the request as these fields are required.
Links
- HumHub Mail API Documentation - Official API documentation for managing mail conversations in HumHub.
