Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Company → Update

AI-generated

Overview

This node integrates with the Twenty CRM API to manage company records among other resources. Specifically, the Update Company operation allows users to modify existing company data in their CRM system by specifying the company ID and the fields to update.

Common scenarios where this node is beneficial include:

  • Keeping company information up-to-date automatically from external data sources.
  • Enriching company profiles with additional details such as domain name, employee count, or address.
  • Automating CRM workflows that require updating company records based on triggers or other system events.

For example, you could use this node to update a company's employee count and address after receiving new data from an HR system.

Properties

Name Meaning
ID The unique identifier of the company record to update (required).
Company Name The official name of the company (required).
Domain The primary domain name of the company, e.g., "example.com".
Employee Count Number of employees working at the company (a numeric value).
Address The street address of the company.

Output

The node outputs JSON data representing the updated company record as returned by the Twenty CRM API. The structure typically includes all the fields of the company resource, reflecting the latest state after the update.

If the node encounters errors during execution, it outputs an error object containing the error message along with the resource and operation context.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Twenty CRM API.
  • The node expects the API base URL and authentication to be configured via n8n credentials.
  • Network connectivity to the Twenty CRM REST API endpoint is necessary.

Troubleshooting

  • Invalid JSON in Fields: If using custom JSON fields (not applicable here but relevant for custom resources), ensure the JSON syntax is correct to avoid parsing errors.
  • Missing Required Fields: The node requires the company ID and company name for updates; omitting these will cause errors.
  • Authentication Errors: Verify that the API key credential is valid and has sufficient permissions.
  • HTTP Request Failures: Network issues or incorrect API URLs can cause request failures; check connectivity and credential configuration.
  • Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.

Links and References

Discussion