Skip to main content

Huntress Integration Identity Matching

Integrations

The new Huntress integration create identity objects using the email address rather than attempting to match an existing object that contains the email address. Since we migrated from IT Glue our roughly 20k identities are created using the actual name of the user.

Different matching options would make this more usable.

3 comments

Log in to comment and vote

Comments3

  • Linked to Huntress Integration Agent Sync

  • Sapphire Geyser

    •

    Oct 27

    100% same issue here, created duplicates across everything we tested, and as per our support ticket this seems to be expected. Our scenario is the same, all our users come in from HaloPSA into Hudu and are a nicely named asset, but the Huntress integration is assuming asset name == email address so just duplicates. The other issue is the single device asset type, which also led to duplicates, and doesn’t really make things usable for servers/workstations in different asset types.

    At this stage the Huntress integration is largely unusable.

    “For users, the integration matches Huntress identities by asset name, within the matched company and the layout selected for Huntress identities. It uses the Huntress username, or the email address if there is no username. The email address is saved on the new card, but it is not currently used to find an existing person. This means a person asset named “First Last” will not be matched, and a second asset named after the email address is created. Deleting those duplicates does not change this, so a later sync will create them again.”

  • Coral Deer

    •

    Oct 22

    So we came from ITGlue where contacts (People) were created using First Name Last Name and during the migration the object is named that way. The Huntress integration pulls in the contact as just email address and did not seem to be matching any fields that were defined on existing objects and just made like 8k new objects that I had to promptly remove.

    The actual card it would make if the matching worked better was nice, but it’s just not usable for us in this state.

  • Aqua Reindeer

    •

    Oct 22

    If i am following this comment… Huntress tries to match using User Name which is not always an option for email addresses like billing@ or accounts@ where as in Halo we have added the users First and Last name manually as the employee using billing@ changes. Huntress manages identities and not users, and should match via email address. I now have double cards because of this.