Actions9
✏️ Update Record
AI-generatedOverview
This node operation updates an existing record in the Inflow CRM system. It is useful when you need to modify specific fields of a record identified by its unique Record ID. For example, updating a customer's contact information or changing the status of an order.
Use Case Examples
- Update a contact's email address in the Contacts module by specifying the Record ID and the new email field value.
- Modify the status of a sales order in the Orders module by providing the Record ID and the updated status field.
Properties
| Name | Meaning |
|---|---|
| 📦 Module | The Inflow CRM module to work with, such as Contacts, Orders, etc. This determines the type of record to update. |
| Record ID | The unique identifier of the record to update in the specified module. |
| Fields | The specific fields and their new values to update in the record. Only the fields provided will be changed. |
| 📎 File Uploads | Optional file uploads associated with the record update. Files can be provided as binary data from a previous node or via file path. |
Output
JSON
id- The unique identifier of the updated record.module- The module in which the record was updated.updatedFields- The fields that were updated with their new values.fileUploadStatus- Status or result of any file uploads performed during the update.
Dependencies
- Inflow CRM API with authentication credentials
Troubleshooting
- Ensure the Record ID is provided and valid; missing or incorrect ID will cause errors.
- Mapped fields must be provided as an object with valid field names; invalid or empty fields will cause the update to fail.
- File uploads require correct binary property names or valid file paths; incorrect file references will cause upload errors.
- API authentication must be correctly configured; authentication failures will prevent the update operation.