Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node allows you to create a new message within the "Messages" resource of the connected API. It is useful for automating the sending or logging of messages in workflows, such as creating support tickets, posting updates, or recording communications programmatically.
For example, you could use this node to automatically create a message when a new customer inquiry arrives, including details like subject, text content, and associated thread information.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested data to include in the response: - 0: Only the primary message object. - 1: Primary message plus directly related objects. - 2: Primary message, related objects, and their related objects. |
| Header Message Id | The identifier of the message header to associate with this message. |
| Subject | The subject line or title of the message. |
| Text | The main textual content/body of the message. |
| Message Thread Id | Identifier of the message thread this message belongs to, linking it to a conversation or discussion thread. |
| Received At | The date/time when the message was received, formatted as a string. |
Output
The node outputs JSON data representing the newly created message object. This includes all properties of the message as returned by the API, potentially enriched with related objects depending on the selected depth level.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The base URL for the API is configured via credentials.
- The node uses standard HTTP headers for JSON communication (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Invalid or missing authentication: Ensure that the API key credential is correctly set up and has sufficient permissions to create messages.
- Incorrect property values: Verify that required fields like
subjectandtextare provided and properly formatted. - Date format issues: The
receivedAtfield should be a valid date string; invalid formats may cause errors. - API limits or errors: If the API returns errors, check the error message for rate limiting or validation issues.
- Depth parameter misuse: Using a higher depth value may increase response size and latency; adjust according to your needs.
Links and References
- Twenty API Documentation (Assumed official docs for the API)
- n8n documentation on Creating Custom Nodes