Update Matcher
hudu_update_matcherUpdate an integration-to-company matcher to resolve unmatched records or redirect synced data to the correct Hudu company.
Instructions
Point an integration record at a Hudu company, or correct which company it points at. A matcher is one row in the mapping table between a connected integration (a PSA or RMM such as Autotask or ConnectWise) and Hudu's companies: it ties one customer record in that external system to one Hudu company, so synced data lands in the right place.
This is how an unmatched record gets resolved, and it is the second half of a two-step job:
Call hudu_list_matchers with the
integration_idandmatched: falseto get the records the sync could not place. Each one gives you itsid, the customernameas the external system spells it, and sometimes apotential_company_idthat Hudu guessed at.Work out the right Hudu company — hudu_list_companies with
searchset to that name is the usual way — and call this tool with the matcheridand thatcompany_id.
Matchers cannot be created through the API; they appear when an integration syncs. So this tool only ever edits rows that already exist, and a matcher id that returns 404 means the sync has not produced that record.
Only the fields you supply are sent, and each replaces the stored value outright.
Operation class: Update. Impact: Changes which Hudu company this integration record maps to, and therefore where future synced data from that record is filed.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric Hudu id of the matcher row, from hudu_list_matchers. | |
| sync_id | No | The record's id inside the integration. Sent as a string, even where the integration numbers its records. Change this only to correct a mis-synced key. | |
| company_id | No | Numeric id of the Hudu company this integration record should map to. Setting this is what resolves an unmatched record; changing it on a matched one redirects future synced data to a different company. | |
| identifier | No | The record's string key inside the integration, for systems that do not use numeric ids. Change this only to correct a mis-synced key. | |
| potential_company_id | No | Hudu's suggested company for this record, which the UI offers as a one-click match. Setting it only changes the suggestion — use `company_id` to actually make the match. |