Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Person → Update
AI-generatedOverview
This node integrates with the Twenty CRM API to manage CRM data programmatically. Specifically, for the Person - Update operation, it updates an existing person record in the CRM system by modifying fields such as first name, last name, email, phone, job title, and city.
Common scenarios where this node is useful include:
- Keeping contact information up-to-date automatically when changes occur in other systems.
- Enriching person records with additional details collected from forms or other sources.
- Synchronizing CRM data with external databases or applications.
For example, if a user's phone number or job title changes, this node can update the corresponding person record in Twenty CRM without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the person record to update (required). |
| First Name | The person's first name. |
| Last Name | The person's last name. |
| The primary email address of the person. | |
| Phone | The primary phone number of the person. |
| Job Title | The job title or position of the person. |
| City | The city where the person is located. |
Output
The node outputs JSON data representing the updated person record as returned by the Twenty CRM API. The structure typically includes the updated fields and metadata about the person.
If multiple input items are processed, the output is an array of JSON objects, each corresponding to one updated record.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Twenty CRM API.
- The node uses the base API URL configured in the credentials.
- No additional external dependencies beyond the Twenty CRM API.
Troubleshooting
- Invalid JSON in Fields: If using custom JSON fields (not applicable here but relevant for custom resources), ensure the JSON syntax is correct.
- Missing or Incorrect ID: The update operation requires a valid person ID; missing or incorrect IDs will cause errors.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Connectivity problems with the Twenty CRM API endpoint may cause request failures.
- Empty Required Fields: While only ID is strictly required for update, providing empty strings for names or emails will overwrite existing data with blanks—use carefully.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and data structures)
- n8n Documentation (for general usage of n8n nodes and credentials)