Actions144
- Activity Log Actions
- API Info Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Export Actions
- Folder Actions
- Group Actions
- IP Address Actions
- List Actions
- List Options Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Photo Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
- Relation Actions
- S3 Export Actions
- Upload Actions
- User Actions
- VLAN Actions
- VLAN Zone Actions
- Website Actions
Matcher → Update
AI-generatedOverview
This node operation updates an existing matcher entity in the Hudu system. It is useful for scenarios where you need to modify details of a matcher, such as changing its associated company, identifier, potential company, or sync ID. For example, you might update a matcher to reflect a new company association or correct an identifier.
Use Case Examples
- Update a matcher to associate it with a different company by specifying the company ID or name.
- Modify the identifier of a matcher to correct or update its value.
- Change the potential company linked to a matcher to reflect new matching criteria.
- Update the sync ID of a matcher to maintain synchronization with external systems.
Properties
| Name | Meaning |
|---|---|
| Matcher ID | The unique numeric ID of the matcher to update. This is required to identify which matcher to modify. |
| Matcher Update Fields | A collection of fields to update on the matcher, including company association, identifier, potential company, and sync ID. |
Output
JSON
id- The unique identifier of the updated matcher.company_id- The company associated with the matcher after update.identifier- The updated identifier of the matcher.potential_company_id- The potential company linked to the matcher after update.sync_id- The updated synchronization ID of the matcher.
Dependencies
- Requires an API key credential for authenticating with the Hudu REST API.
Troubleshooting
- Common issues include providing an invalid matcher ID, which results in an error indicating the matcher was not found.
- Incorrect or missing required fields in the update collection can cause the update to fail.
- API authentication errors if the API key credential is missing or invalid.
- Errors thrown by the node will include messages that help identify if the resource or operation is unknown or unsupported.