Does IT Glue integrate with Rewst?
Sync depth, webhook support, known API limits and setup order for the IT Glue + Rewst pairing.
Compatibility index
96/100
Rewst Crate available (Verified)
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 Rewst
Devices / assetsIT Glue Rewst
TicketsRewst IT Glue
Time & billingRewst IT Glue
RE
Rewst
Billing & CPQ
API A
Integration checklist
- Bidirectional ticket / alert sync
Alerts raise tickets and status changes flow back without middleware.
- Asset / device mapping
Devices match to client records automatically after the initial mapping pass.
- Alert escalation rules
Severity maps to priority and on-call routing rules travel with the alert.
- Billing reconciliation
Seat counts reconcile to invoices automatically each cycle.
- Webhook / event support
Both sides expose event webhooks (API grades B and A).
Common bottlenecks & caveats
- Seat minimums apply (IT Glue: 5, Rewst: 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.
Other Billing & CPQ options with native IT Glue sync
IT Glue + Rewst: frequently asked questions
- Does IT Glue integrate with Rewst?
- Yes — IT Glue and Rewst have a native integration. Rewst Crate available (Verified) The pairing scores 96 out of 100 on our compatibility index.
- How do you set up IT Glue with Rewst?
- Create an API user or integration key in IT Glue, authorise it in Rewst, 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 + Rewst integration?
- Seat minimums apply (IT Glue: 5, Rewst: 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.