Does IT Glue integrate with DNSFilter?

Sync depth, webhook support, known API limits and setup order for the IT Glue + DNSFilter pairing.

Compatibility index
56/100

No documented native integration between IT Glue and DNSFilter.

No native integration
API depth: grades B / AMulti-tenancy: 5/5 and 5/5Webhook events: supported both sides

Data flow diagram

How records move between the two systems once the integration is enabled.

IT
IT Glue
Documentation
API B
AlertsIT Glue DNSFilter
Devices / assetsIT Glue DNSFilter
TicketsDNSFilter IT Glue
Time & billingDNSFilter IT Glue
DN
DNSFilter
DNS / Network
API A

Integration checklist

  • Bidirectional ticket / alert sync

    No vendor-supported path; needs a webhook relay or automation platform.

  • Asset / device mapping

    Assets must be reconciled manually or via CSV import.

  • Alert escalation rules

    Escalation logic has to live in one system; expect duplicated rule sets.

  • Billing reconciliation

    Neither product owns billing — reconcile through your billing/PSA layer.

  • Webhook / event support

    Both sides expose event webhooks (API grades B and A).

Common bottlenecks & caveats

  • Sync depth is non-existent — budget technician time or an automation platform such as Rewst.
  • Seat minimums apply (IT Glue: 5, DNSFilter: none) — small tenants pay for unused units.
  • Field mapping is not retroactive: records created before the integration is enabled usually need a one-time backfill.

IT Glue + DNSFilter: frequently asked questions

Does IT Glue integrate with DNSFilter?
There is no documented native integration between IT Glue and DNSFilter. The pairing scores 56 out of 100, so plan on a webhook relay or an automation platform to move events between them.
How do you set up IT Glue with DNSFilter?
Create an API user or integration key in IT Glue, authorise it in DNSFilter, map clients or tenants to each other once, then map alert severities to ticket priorities. Historic records created before the integration is enabled usually need a one-time backfill.
What are the known limitations of the IT Glue + DNSFilter integration?
Sync depth is non-existent — budget technician time or an automation platform such as Rewst. Seat minimums apply (IT Glue: 5, DNSFilter: none) — small tenants pay for unused units. Field mapping is not retroactive: records created before the integration is enabled usually need a one-time backfill.