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 operation allows users to create multiple message channels in bulk via the Twenty API. It is useful when you need to programmatically set up many communication channels at once, such as email or other messaging types, with specific synchronization and visibility settings. Typical use cases include initializing messaging infrastructure for a new project, migrating data, or automating channel creation workflows.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information is included in the response: - 0: Only the primary message channel objects. - 1: Primary objects plus their directly related objects. - 2: Includes related objects of those related objects as well. |
| Body | JSON object defining the message channels to create. Example fields include: - syncStage: Status of message list synchronization.- syncStatus: Current sync progress.- contactAutoCreationPolicy: Policy for auto-creating contacts.- type: Type of message channel (e.g., "email").- visibility: Visibility level of the channel metadata. |
Output
The node outputs JSON data representing the created message channels. The structure includes the primary message channel objects and, depending on the selected depth, their related nested objects. This output can be used downstream in workflows to reference newly created channels or to verify creation success.
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 dynamically from credentials.
- The node sends requests with
Content-TypeandAcceptheaders set toapplication/json.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the Body property is malformed, the request will fail. Ensure valid JSON syntax.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
- API Limits or Permissions: Creating many channels at once may hit rate limits or require specific permissions. Check API documentation and credentials scope.
- Depth Parameter Misuse: Setting an unsupported depth value could lead to unexpected responses or errors. Use only 0, 1, or 2 as defined.
Links and References
- Twenty API Documentation (Assumed official docs for further details on message channels and API usage)
- n8n Documentation on Creating Custom Nodes