Actions104
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Meeting Actions
- Meeting Room Actions
- Meeting Type Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Ticket Actions
- Treatment Actions
- Treatment Type Actions
- Workspace Actions
Customer → Update
AI-generatedOverview
This node updates an existing customer record in the Magnet Customer system. It is useful for scenarios where you need to modify customer details such as contact information, address, custom fields, and other personal or business-related data. For example, you can update a customer's email, phone numbers, address, or custom attributes programmatically within an automation workflow.
Use Case Examples
- Updating a customer's email and phone number after receiving new contact information.
- Modifying a customer's address and adding custom fields for additional data tracking.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use for the API request (API Token or OAuth2). |
| Contact ID | The unique identifier of the customer to update. |
| Fullname | The full name of the customer. |
| The email address of the customer. | |
| Phones | A collection of phone numbers to add or update for the customer. |
| Gender | The gender of the customer (Male or Woman). |
| Birthdate | The birthdate of the customer. |
| Work | The work or occupation of the customer. |
| Marital Status | The marital status of the customer. |
| Document (CPF/CNPJ) | The document identifier of the customer (e.g., CPF or CNPJ). |
| Legal Type | The legal type of the customer (Physical or Legal entity). |
| State | The state where the customer is located. |
| City | The city where the customer is located. |
| Address | The address of the customer. |
| Address Number | The address number of the customer. |
| Complement Address | Additional address information or complement. |
| Neighborhood | The neighborhood of the customer. |
| CEP | The postal code (CEP) of the customer. |
| Owners | Owners associated with the customer. |
| Custom Fields | Custom fields to set additional values not predefined in the standard fields. |
| Encode Custom Fields | Whether to automatically encode custom fields and option fields as IDs instead of names or values. |
Output
JSON
_id- The unique identifier of the updated customer.fullname- The full name of the updated customer.email- The email address of the updated customer.phoneCollection- The collection of phone numbers associated with the updated customer.gender- The gender of the updated customer.birthDate- The birthdate of the updated customer.work- The work or occupation of the updated customer.maritalStatus- The marital status of the updated customer.doc- The document identifier of the updated customer.type- The legal type of the updated customer.state- The state of the updated customer.city- The city of the updated customer.address- The address of the updated customer.addressNumber- The address number of the updated customer.complement- The complement address of the updated customer.neighborhood- The neighborhood of the updated customer.cep- The postal code (CEP) of the updated customer.owners- The owners associated with the updated customer.customFieldCollection- The collection of custom fields set for the updated customer.
Dependencies
- Magnet Customer API
- API Token or OAuth2 credentials
Troubleshooting
- Ensure the Contact ID is valid and exists in the Magnet Customer system to avoid 'not found' errors.
- Verify that the authentication credentials (API Token or OAuth2) are correctly configured and have sufficient permissions.
- If custom fields are used, ensure they are correctly encoded or resolved based on the 'Encode Custom Fields' option to prevent data format errors.