Actions16
Overview
This node integrates with the Outseta CRM API to update an existing person's details in the CRM system. It allows users to modify various attributes of a person, such as their email, first name, last name, and additional contact information like mobile and work phone numbers or timezone.
Common scenarios for this node include:
- Keeping contact information up-to-date when a person changes their email or phone number.
- Correcting or adding missing personal details in the CRM.
- Synchronizing user data from other systems into Outseta CRM.
For example, if a customer updates their contact info on a website, this node can be used to reflect those changes in the Outseta CRM automatically.
Properties
| Name | Meaning |
|---|---|
| Person UID | The unique identifier of the person to update (required). |
| The updated email address of the person. | |
| First Name | The updated first name of the person. |
| Last Name | The updated last name of the person. |
| Additional Fields | Optional extra fields to update: - Mobile Phone - Work Phone - Timezone |
Output
The node outputs the JSON response returned by the Outseta CRM API after updating the person. This typically includes the updated person object with all current properties reflecting the changes made.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Outseta CRM API.
- Needs the domain URL of the Outseta instance configured in credentials.
- The node sends HTTP PUT requests to the endpoint
/crm/people/{personUid}to perform the update.
Troubleshooting
- Missing Person UID: The update operation requires the unique identifier of the person. Omitting this will cause an error.
- Invalid or expired API key: Authentication failures will prevent updates; ensure the API key is valid and has necessary permissions.
- Incorrect field names or formats: Providing invalid data types or unsupported fields may result in API errors.
- Network issues: Connectivity problems can cause request failures; verify network access to the Outseta API endpoint.
Error messages usually come directly from the Outseta API and should be checked against their documentation for resolution steps.
Links and References
- Outseta API Documentation (for detailed API endpoints and data models)
- n8n Documentation on HTTP Request Node (conceptual understanding of API calls)