Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node interacts with the "Matcher" resource of an external system via its API, specifically supporting the Update operation. It allows users to update existing matcher records by specifying the matcher ID and the fields to modify. This is useful in scenarios where you need to programmatically maintain or correct matcher data, such as updating identifiers, associating matchers with different companies, or changing synchronization IDs.
Practical examples include:
- Updating a matcher’s identifier after a data correction.
- Changing the company association of a matcher when organizational changes occur.
- Adjusting the sync ID to align with external synchronization processes.
Properties
| Name | Meaning |
|---|---|
| Matcher ID | The unique numeric ID of the matcher to update. |
| Update Fields | A collection of fields to update on the matcher. Options include: |
| - Company Name or ID | Select or specify the company to associate with the matcher. Can be chosen from a list or set via expression. |
| - Identifier | The new identifier string for the matcher. |
| - Potential Company Name or ID | Select or specify the potential company to be matched. Similar selection options as company_id. |
| - Sync ID | Numeric sync ID to update the matcher’s synchronization reference. |
Output
The node outputs an array of JSON objects representing the updated matcher records. Each output item corresponds to an input item processed and includes the updated matcher data as returned by the API.
If errors occur during processing and the node is configured to continue on failure, the output will include error messages associated with the respective input items.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating requests to the external system's REST API.
- The base URL for the API must be configured in the node credentials.
- The node relies on internal helper methods to load options dynamically (e.g., companies list) for user-friendly selection.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Matcher ID will likely result in an error from the API.
- Omitting required fields or providing invalid field types in the update collection may cause request failures.
- Network or authentication issues can prevent successful API calls.
Error Messages:
- Errors thrown by the node typically include the API response message. For example, "Matcher not found" indicates an invalid ID.
- Authentication errors suggest checking the API key and base URL configuration.
- If the node fails on one item but is set to continue on fail, error details are included in the output JSON for that item.
Links and References
- n8n Expressions Documentation — for using expressions in property values.
- External API documentation (not provided here) should be consulted for detailed matcher resource schema and update semantics.