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 users to create multiple company records in bulk via the "Create Many Companies" operation under the "Companies" resource. It is useful for scenarios where you need to add a batch of companies into a system that supports nested related objects, such as CRM platforms or business directories. For example, you might use this node to import a list of new client companies along with their associated domain and social media links, streamlining data onboarding.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related object information is included in the response: - 0: Only the primary company information. - 1: Primary company plus directly related objects (no further nesting). - 2: Primary, directly related, and related objects of those related objects. |
| Body | JSON object representing one or more companies to create. Includes fields like company name, domain links, LinkedIn links, other external links, and financial info such as annual recurring revenue. The structure supports nested objects for detailed company data. |
Output
The node outputs JSON data representing the created company records. The output includes the primary company details and, depending on the selected depth, nested related objects up to two levels deep. This enables downstream nodes to access comprehensive company data immediately after creation.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating requests to the external service providing the company management API.
- The node uses a base URL configured from credentials.
- The node depends on an OpenAPI specification (
twenty-v1.0.3-openapi.json) bundled internally to define its properties and request structure. - No additional environment variables are explicitly required beyond standard API authentication.
Troubleshooting
- Invalid JSON in Body: Since the body property expects valid JSON, malformed input will cause errors. Ensure the JSON syntax is correct before execution.
- Authentication Errors: Missing or invalid API credentials will prevent successful requests. Verify that the API key or token is correctly configured.
- Depth Parameter Misuse: Setting an unsupported depth value outside 0, 1, or 2 may lead to unexpected responses or errors.
- API Rate Limits: Bulk creation operations might hit rate limits; monitor API usage and consider splitting large batches if necessary.
Links and References
- OpenAPI Specification Reference (bundled with the node)
- General n8n documentation on Creating Custom Nodes
- Typical REST API best practices for bulk creation endpoints