Actions60
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Deals Actions
- Webhooks Actions
- Contacts Actions
- Companies Actions
- Bussiness Types Actions
- Tags Actions
- Deal Phases Actions
- Invoices Actions
- Subscriptions Actions
- Products Actions
- Projects Actions
- Tasks Actions
- Files Actions
Overview
The "Update Contact" operation in this node allows users to modify existing contact records within the Teamleader system via its API. This is useful for keeping contact information current, such as updating names, website URLs, birthdays, language preferences, remarks, marketing consent status, and company associations.
Typical scenarios include:
- Updating a contact's last name or other personal details after receiving new information.
- Changing the company a contact is linked to.
- Adjusting marketing mail consent status based on user preferences.
- Adding remarks or notes about the contact.
For example, a sales team could automate updating contact details when a lead provides updated information during a call or meeting.
Properties
| Name | Meaning |
|---|---|
| First Name | The first name of the contact (optional). |
| Last Name | The last name of the contact (required). |
| Salutation | The salutation of the contact (e.g., Mr., Ms.) (optional). |
| Website | The website URL associated with the contact (optional). |
| Birthday | The birthday of the contact in YYYY-MM-DD format (optional). |
| Language | The preferred language of the contact (optional). |
| Remarks | Additional remarks or notes about the contact (optional). |
| Marketing Mails Consent | Boolean indicating if the contact has consented to receive marketing emails (optional). |
| Company ID | The ID of the company the contact is linked to (required). |
| ID | The unique identifier of the contact to update (required). |
Output
The node outputs an array of JSON objects representing the updated contact data returned by the Teamleader API. Each object corresponds to one updated contact record.
The output JSON structure reflects the fields returned by the API after the update operation, typically including the contact's identifiers and updated properties.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions.
- The node communicates with the Teamleader API endpoint at
https://api.focus.teamleader.eu. - Proper API authentication token must be provided via n8n credentials.
Troubleshooting
- Missing Required Fields: If required fields like "Last Name", "Company ID", or "ID" are missing, the API will reject the request. Ensure these are provided.
- Invalid Date Format: The "Birthday" field must be in
YYYY-MM-DDformat; otherwise, the API may return an error. - API Authentication Errors: If the OAuth2 token is invalid or expired, requests will fail. Refresh or reconfigure credentials as needed.
- No Data Returned: If the API returns no data, the node reports "No data got returned". Verify that the contact ID exists and the API is reachable.
- Continue On Fail: If enabled, errors for individual items will be captured in the output instead of stopping execution.
Links and References
- Teamleader API Documentation
- Teamleader Contacts API Reference (for detailed field descriptions and API behavior)