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 creating multiple message participants in bulk within a messaging context. It is useful when you need to add several participants to a message thread or conversation simultaneously, such as when initializing group chats or adding users to an existing discussion.
Practical examples include:
- Adding a list of users to a new group message.
- Bulk inviting participants to a conversation.
- Automating participant management in messaging workflows.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested data is included in the response: - 0: Only the primary message participant objects. - 1: Primary objects plus their directly related objects. - 2: Includes related objects of those related objects as well. |
| Body | JSON object representing the message participants to create. This should contain the details of each participant, for example specifying roles like "role": "from". The body must be valid JSON and defines the participants' data. |
Output
The output json field contains the created message participant objects. Depending on the Depth property, this can include just the primary participant data or also nested related objects up to two levels deep.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate with the external Twenty API service.
- The node uses the Twenty API base URL configured via credentials.
- The request content type is JSON, and responses are expected in JSON format.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the Body property is malformed, the node will fail. Ensure the JSON syntax is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Depth Value Issues: Providing an unsupported depth value (other than 0, 1, or 2) may result in unexpected responses or errors.
- API Limits or Permissions: Creating many participants at once might hit API rate limits or permission restrictions; check API documentation and credentials permissions.
Links and References
- Twenty API Documentation (general reference for the API endpoints and data structures)
- JSON formatting tools for validating the Body input before use.