Skip to main content
Triggr works with IT Glue organisations, contacts, locations, passwords, configurations, documents, flexible assets, checklists and account data.

​
Set up IT Glue

You need an IT Glue Enterprise plan and the Administrator role.
1

Generate a custom key

Go to Admin > Settings > API Keys. Under Custom API Keys, click Create API Key, name it Triggr and click Generate API Key.
2

Choose password access

Tick Password Access only if workflows need to read or store password values. It lets anyone with the key read every stored password through the API.
3

Copy the key

Copy the key, which starts with ITG.. IT Glue shows it only once.
See IT Glue’s Getting started with the IT Glue API.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > IT Glue and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the key and data centre

Paste the key into ApiKey. Leave Hostname as https://api.itglue.com, or enter https://api.eu.itglue.com (EU) or https://api.au.itglue.com (Australia) for your data centre, then click Save Configuration.
The IT Glue configuration window with an ApiKey field, a Hostname field set to https://api.itglue.com, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
One connection covers your whole account, with no client mapping. Workflows find a client’s organisation with List Organizations, filtered by name or PSA ID.

​
Troubleshooting

Paste the key again in full, check it’s active (not paused) under Admin > Settings > API Keys, and check Hostname starts with https:// and matches your data centre. If Admin > Settings > IP Access Control is set to Allow specific IP addresses, add Triggr’s IP addresses.
IT Glue revokes keys unused for 90 days. Generate a new key and paste it into ApiKey.
Tick Password Access on Triggr’s key, then rerun the workflow.
IT Glue rejects API updates to an organisation that’s syncing with your PSA.