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 updates a single company record in the connected service. It allows users to modify various attributes of a company such as its name, website URL, employee count, social media links, revenue, address, and other metadata. This is useful for keeping company data up-to-date within workflows that manage CRM data, marketing lists, or business intelligence systems.
Practical examples include:
- Automatically updating company details when new information is received from another system.
- Enriching company records with additional data like LinkedIn or Twitter profiles.
- Adjusting company status or ownership information based on workflow logic.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the company object to update. |
| Depth | Level of nested related objects to include in the response: 0 (only primary object), 1 (primary + directly related objects), 2 (primary + related + their related objects). |
| Name | The company's name. |
| Domain Name | The company's website URL, used to fetch the company icon. Expected as a JSON object. |
| Employees | Number of employees in the company. |
| Linkedin Link | The company's LinkedIn account link, provided as a JSON object. |
| X Link | The company's Twitter/X account link, provided as a JSON object. |
| Annual Recurring Revenue | The actual or estimated annual recurring revenue of the company, provided as a JSON object. |
| Address | The company's address, provided as a JSON object. |
| Ideal Customer Profile | Boolean indicating whether this company is an ideal customer profile (most suitable and valuable customer). |
| Position | The position or ranking of the company record. |
| Created By | Information about the creator of the record, provided as a JSON object. |
| Account Owner Id | Identifier of the account owner associated with the company. |
Output
The node outputs the updated company object in the json field of the output data. The structure reflects the updated company properties including any nested related objects depending on the selected depth level. If binary data were involved (not indicated here), it would typically represent files or images related to the company, but this operation focuses on JSON data only.
Dependencies
- Requires an API key credential to authenticate requests to the external Twenty API service.
- The base URL for the API is configured via credentials.
- The node uses HTTP headers to accept and send JSON content.
- No additional environment variables are explicitly required beyond standard API authentication.
Troubleshooting
- Invalid or missing Id: The update operation requires a valid company ID. Ensure the "Id" property is correctly set; otherwise, the API will reject the request.
- Malformed JSON inputs: Several properties expect JSON objects (e.g., domainName, linkedinLink). Invalid JSON syntax will cause parsing errors. Validate JSON formatting before input.
- API authentication errors: Missing or incorrect API credentials will result in authorization failures. Verify that the API key credential is properly configured.
- Depth parameter misuse: Setting an unsupported depth value may lead to unexpected responses or errors. Use only 0, 1, or 2 as allowed.
- Network or connectivity issues: Standard network troubleshooting applies if the node cannot reach the API endpoint.
Links and References
- Twenty API Documentation (hypothetical link for reference)
- n8n documentation on Creating Custom Nodes
- JSON validation tools such as JSONLint for verifying JSON inputs