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 you to create multiple "View Groups" in a batch. It is useful when you need to programmatically add several view groups at once, for example, when setting up or updating configurations that involve grouping views in a system. This can save time compared to creating each view group individually.
A practical example would be automating the setup of user interface components or dashboards where multiple view groups define different sections or filters.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much nested related object information is included in the response: - 0: Only the primary object's information. - 1: Primary object plus its directly related objects. - 2: Primary object, its related objects, and their related objects. |
| Body | JSON object representing the data for the view groups to create. This should include the necessary fields such as fieldMetadataId and any other required properties for the view groups. |
Output
The output contains a JSON field with the created view groups' details. The structure reflects the newly created objects including any nested related objects depending on the selected depth level. This allows you to immediately use or reference the created view groups in subsequent workflow steps.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate requests to the external Twenty API service.
- The node uses the Twenty API base URL configured via credentials.
- The request headers specify JSON content type and accept JSON responses.
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 Parameter Misuse: Using unsupported depth values may result in unexpected responses or errors. Use only 0, 1, or 2 as specified.
- API Limitations: Creating many view groups at once might hit API rate limits or payload size restrictions. Consider batching requests if errors occur.
Links and References
- Twenty API Documentation (hypothetical link for the API used)
- n8n Documentation on Creating Custom Nodes