Actions68
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Workspace Actions
Overview
This node integrates with the Magnet Customer API to update existing deals in a CRM system. It allows users to modify various attributes of a deal such as its title, description, associated organization or contact, pipeline stage, expected closing date, status, assigned user, amount, and custom fields.
Common scenarios where this node is beneficial include:
- Automating updates to sales deals based on external triggers or workflows.
- Synchronizing deal information from other systems into Magnet Customer.
- Managing deal pipelines programmatically by moving deals between stages or updating their statuses.
Practical example:
- When a lead converts to a customer in another system, this node can update the corresponding deal's status to "won" and assign it to the appropriate sales staff member automatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either an API Token or OAuth2. |
| Deal ID | The unique identifier of the deal to update (required). |
| Title | The new title for the deal (required). |
| Description | A textual description of the deal. |
| Associate With | Specifies whether the deal should be linked to an Organization or a Contact. Options: organization, contact. |
| Organization ID | The ID of the organization to associate the deal with (shown if "Associate With" is set to Organization). |
| Contact ID | The ID of the contact to associate the deal with (shown if "Associate With" is set to Contact). |
| Pipeline Name or ID | The pipeline in which the deal will be placed. If omitted, defaults to the first stage of the default pipeline. Users can select from a list or specify an ID via expression. |
| Stage Name or ID | The stage within the pipeline where the deal will be placed. If omitted, defaults to the first stage of the default pipeline. Selectable from a list or via expression. |
| Expectation of Closing | The expected closing date/time for the deal. |
| Status | The current status of the deal. Options: open, won, lost, deleted. Defaults to open if not provided. |
| User Name or ID | The ID of the active user to whom the deal activity will be assigned. If omitted, defaults to the authorized user. Selectable from a list or via expression. |
| Amount | The monetary value of the deal. Defaults to 0 if not set. |
| Custom Fields | Allows setting additional custom fields that are not predefined. Each custom field requires a field name or ID and a value. |
| Encode Custom Fields | Boolean flag indicating whether custom fields should be automatically encoded (IDs used instead of names/values). Useful when custom fields require IDs rather than human-readable names. |
Output
The node outputs JSON data representing the updated deal object(s) returned from the Magnet Customer API after the update operation. This typically includes all standard and custom fields of the deal reflecting the new state.
No binary data output is produced by this node.
Dependencies
- Requires access to the Magnet Customer API.
- Requires valid authentication credentials configured in n8n, either an API token or OAuth2 credentials.
- Uses internal methods to load options dynamically for pipelines, stages, organizations, contacts, staff, and custom fields.
- No additional external dependencies beyond the Magnet Customer API.
Troubleshooting
- Missing or invalid Deal ID: The update operation requires a valid deal ID. Ensure the ID corresponds to an existing deal in the system.
- Authentication errors: Verify that the API token or OAuth2 credentials are correctly configured and have sufficient permissions.
- Invalid pipeline or stage IDs: If specifying pipeline or stage, ensure the IDs exist and are accessible by the authenticated user.
- Custom fields encoding issues: If custom fields are not updating correctly, try toggling the "Encode Custom Fields" option to match the expected format (ID vs. name).
- API rate limits or connectivity issues: Network problems or API limits may cause failures; check connectivity and API usage quotas.
- Error messages usually contain the API error message; review them to identify missing required fields or invalid values.
Links and References
- Magnet Customer API Documentation
- n8n Expressions Documentation
- n8n Custom Fields Handling (hypothetical link for custom fields guidance)