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 you to create a new company record in the connected service via its API. It is useful for automating the addition of company data into your CRM or business database, especially when integrating with other workflows that generate or collect company information.
Typical use cases include:
- Automatically adding new leads or prospects as companies.
- Enriching your database with detailed company profiles.
- Syncing company data from external sources or forms.
For example, after capturing a lead's details from a web form, you can use this node to create a corresponding company entry with relevant attributes like name, website, employee count, and social media links.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much nested related object data to include in the response: 0 (only primary company info), 1 (primary + directly related objects), or 2 (primary + related + their related objects). |
| Name | The name of the company to create. |
| Domain Name | The company's website URL, used to fetch the company icon. Accepts JSON format. |
| Employees | Number of employees in the company. |
| Linkedin Link | The LinkedIn account of the company, provided as JSON. |
| X Link | The Twitter/X account of the company, provided as JSON. |
| Annual Recurring Revenue | The actual or estimated annual recurring revenue of the company, provided as JSON. |
| Address | The physical address of the company, provided as JSON. |
| Ideal Customer Profile | Boolean indicating if the company is considered an ideal customer profile (most suitable and valuable customer). |
| Position | Numeric position or ranking of the company record. |
| Created By | Information about the creator of the record, provided as JSON. |
| Account Owner Id | Identifier string for the account owner associated with the company. |
Output
The node outputs the created company data in the json field of the output item. This includes all the properties sent plus any additional metadata or identifiers returned by the API. The depth property controls how much nested related data is included in the response.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential to authenticate requests to the Twenty API.
- The base URL for the API is configured via credentials.
- The node uses JSON-formatted input for complex fields such as domainName, linkedinLink, xLink, annualRecurringRevenue, address, and createdBy.
Troubleshooting
- Invalid JSON in complex fields: Since several properties expect JSON input, malformed JSON will cause errors. Ensure JSON syntax is correct.
- Missing required fields: The company name is essential; omitting it may result in API errors.
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Depth parameter misuse: Setting an unsupported depth value might cause unexpected responses or errors.
- API rate limits or connectivity issues: Network problems or hitting API limits can cause failures; check network and API status.
Links and References
- Twenty API Documentation (hypothetical link, replace with actual)
- n8n documentation on working with JSON parameters