Integrations
Tagaris is a register. Its integrations either feed it or link out from it, and none of them is an agent.
How integrations fit
Feeds the register
Intune devices Jamf Pro devices Entra ID people Snipe-IT and GLPI migration Sign-in from your identity providerOut from the register
Jira tickets Email alerts Slack and Teams webhooks Calendar feed REST APIThe register is the product. Everything else connects to it in one of two directions. Inbound, device sync pulls managed devices from your MDM so the register does not depend on typing, the Entra import pulls people from your directory, the migration page reads a Snipe-IT or GLPI through its API, and single sign-on hands the login to your identity provider (Microsoft Entra ID, Okta, Google Workspace or any OpenID Connect provider). Outbound, Jira takes tickets to your service desk and reads their status back, the REST API lets your own tools read and write records, and email, webhooks and the calendar feed carry alerts to where people already look.
Nothing runs on the devices themselves. There is no Tagaris agent to deploy and nothing to keep patched on endpoints. The inbound connectors are read-only against their source: Tagaris never writes to Intune, Jamf Pro or Entra ID. Each integration is configured in Settings by an administrator (single sign-on by the install owner), tested from the same screen with a real call, and switched off from the same place.
What connects
Five have their own page. The rest are covered in the documentation.
Microsoft Intune
FreeStill in testing
Pulls managed devices from Intune into a review queue, matched to your assets by serial number, then hostname. Link, import or ignore each one. Read-only.
Jamf Pro
FreeStill in testing
The same review queue for the Macs, iPhones and iPads managed in Jamf Pro, with CPU, RAM and storage read from the inventory.
Single sign-on
Free
OpenID Connect with Microsoft Entra ID, Okta, Google Workspace or any other provider (Keycloak, Authentik, JumpCloud, OneLogin, AD FS), with directory groups mapped to roles and access groups, and an option to require it. View-only sign-ins are free and unlimited.
Microsoft Entra ID people import
FreeStill in testing
Pulls enabled users from your directory into the register as people to assign kit to, matched by email, through the same preview as a CSV. Read-only against the directory.
Snipe-IT and GLPI
Free
The migration page reads the old system through its API and brings the register across with a preview first. A second run creates nothing that is already here.
Jira Cloud
Free
Raise a ticket from an asset page with the details filled in, link tickets by issue key, and see the cached status on the asset. Tagaris creates issues and reads status; it never changes a ticket.
REST API
Free
A versioned API for assets, people, locations, issues, vendors and purchase orders, with personal and organisation keys capped at each person's permissions, read and write scopes, a rate limit and an install-wide off switch.
Free
The daily digest, invites and password resets go out over SMTP, Microsoft 365 with OAuth through Graph, or Google Workspace through the Gmail API. A test button reports the exact error if sending fails.
Slack, Microsoft Teams and calendar
Free
Post the daily digest's findings to a Slack or Teams incoming webhook, and subscribe Outlook or Google Calendar to a feed of upcoming renewal dates.
Any service desk, by URL
FreeNo setup
Paste a ticket's URL from Halo, ServiceNow, Zendesk or anything else onto an asset's Tickets card, with an optional label. The link opens the ticket in the other system.
Which tier includes what
Assets are unlimited and every integration is on every tier. Three are still in testing, free and open, with no key to request.
Free
- Email over SMTP, Microsoft 365 or Google Workspace
- Slack and Microsoft Teams webhooks
- Calendar feed of renewal dates
- Ticket links by URL from any service desk
- CSV import with Snipe-IT and Halo presets
- Migration from Snipe-IT and GLPI over their APIs
- Single sign-on with Microsoft Entra ID, Okta, Google Workspace or any OpenID Connect provider
- Jira Cloud ticketing, and issues handed to Jira
- REST API with personal and organisation keys
Free, still in testing
- Microsoft Intune device sync
- Jamf Pro device sync
- Microsoft Entra ID people import
The three still in testing work without a key. They have not yet been proven across a range of real tenants, so tell [email protected] how they behave on yours. Plans are on the pricing page; the free tier is described on the free tier page.
Where each one is set up
Settings, Integrations
The Intune, Jamf Pro and Jira cards live here, for organisation administrators. Each has a Test connection button that signs in and makes a real read, so a green result means the permission is consented and the pull will work.
Each card also takes an optional credential expiry date. The daily digest then warns 30, 7 and 1 days before the secret or token lapses.
Settings, Email and Alerts
The Email tab holds the transport and its test button. The Alerts tab holds the digest thresholds, the Slack and Teams webhooks, the calendar feed and, with Jira connected, the option to raise a ticket from each digest.
Settings, Application, Single sign-on
Single sign-on belongs to the whole install, so it is configured by the install owner rather than an organisation administrator. Choose the provider and the form asks for what it needs: a tenant ID, an Okta domain, or an issuer URL. The same split covers the licence and API kill switch, and is enforced on the server.
People, Import
The Entra people import sits with the CSV importer, and runs through the same preview before anything is written. API keys are created in My account (personal) or Settings (organisation).
Common questions
Does Tagaris install anything on the devices?
No. There is no Tagaris agent. Device details come from Microsoft Intune or Jamf Pro, which already manage the device, and Tagaris reads them through those products' APIs on a schedule.
Can an integration change data in Intune, Jamf, Entra ID or Jira?
The device sync and the people import are read-only: Tagaris never writes to Intune, Jamf Pro or Entra ID. The Jira integration creates issues and reads their summary and status. It never transitions, comments on, edits or deletes a ticket.
Do I need a paid licence for device sync?
No. Device sync from Intune and Jamf Pro, and the Entra ID people import, are free and open on every plan, with no key to request. They are marked still in testing because they have not yet been proven across a range of real tenants; tell [email protected] how they behave on yours.
Which single sign-on providers work?
Microsoft Entra ID, Okta, Google Workspace and any OpenID Connect provider such as Keycloak, Authentik, JumpCloud, OneLogin or AD FS. Directory groups map to roles and access groups. SAML and LDAP are not supported. On every plan.
Can I feed Tagaris from a system that has no connector?
Yes. The CSV importer takes a header row and a column mapping, with presets for Snipe-IT and Halo exports, and the migration page reads Snipe-IT and GLPI through their APIs. The REST API reads and writes assets, people, locations, issues, vendors and purchase orders for your own scripts. All on every plan.
See the register the integrations feed
The live demo runs the current release in your browser, with the Integrations, Alerts and Tickets screens in place.