Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation updates an existing Matcher entity by its unique identifier. It is useful in scenarios where you need to modify specific details of a Matcher record, such as associating it with a different company, updating synchronization identifiers, or changing its unique identifier string. For example, if a Matcher was initially linked to the wrong company or needs to be synchronized with updated external data, this operation allows precise updates without creating new records.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric ID of the Matcher to update. |
| Additional Body Fields | Optional fields to update on the Matcher: |
| - Company Id | Numeric ID representing the updated company associated with the Matcher. |
| - Potential Company Id | Numeric ID for an alternative or potential company association. |
| - Sync Id | String identifier used for synchronization purposes. |
| - Identifier | Updated string identifier for the Matcher. |
Output
The output JSON will contain the updated Matcher object reflecting the changes made. This typically includes all standard Matcher properties such as its ID, company associations, sync identifiers, and any other relevant metadata after the update operation completes successfully.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication to the external service managing Matchers.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests with JSON payloads to communicate with the external API.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Matcher ID will likely result in an error indicating that the resource could not be found.
- Omitting required authentication credentials or misconfiguring the API base URL will cause authorization or connection errors.
- Sending invalid data types (e.g., strings instead of numbers) for numeric fields may cause validation errors.
Error Messages:
- "Matcher not found": Verify the provided Id corresponds to an existing Matcher.
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up and valid.
- "Invalid request body": Ensure all fields conform to expected types and formats.
Links and References
- Refer to the external API documentation for detailed Matcher schema and update endpoint specifications.
- n8n documentation on configuring API credentials and HTTP request nodes for further customization.