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 interacts with the Twenty API to create multiple blocklists in a single operation. It is useful when you need to batch-create several blocklists efficiently, for example, when setting up or updating security filters or content restrictions across multiple categories or sources at once.
Practical scenarios include:
- Automating the creation of multiple blocklists for different types of unwanted content.
- Bulk importing blocklist data from external sources.
- Managing large-scale filtering rules in a centralized manner.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information is included in the response: - 0: Only the primary blocklist objects. - 1: Primary objects plus their directly related objects. - 2: Includes related objects of those related objects as well. |
| Body | JSON object representing the blocklists to be created. This should contain the details of the blocklists in the format expected by the API. |
Output
The node outputs JSON data representing the created blocklists. The structure includes the primary blocklist objects and, depending on the Depth parameter, may also include nested related objects up to two levels deep. This output allows further processing or verification of the created blocklists within an n8n workflow.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The node uses the base URL provided by the credential configuration.
- 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 before running.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key or token is correctly configured.
- API Limits or Quotas: Creating many blocklists at once might hit rate limits imposed by the API. Check the API documentation for any such constraints.
- Incorrect Depth Value: Using unsupported depth values may result in unexpected responses or errors. Use only 0, 1, or 2 as specified.
Links and References
- Twenty API Documentation (Assumed official API docs for reference)
- n8n Documentation on HTTP Request Nodes (For understanding JSON body and query parameters usage)