NinjaOne
Tidehawk raises NinjaOne tickets for expiring certificates and domain registrations.
Before you start
Section titled “Before you start”- You need the owner or admin role in Tidehawk.
- Create an API application in NinjaOne under Administration › Apps › API.
- Set the application’s redirect URI to
https://app.tidehawk.co/api/integrations/ninjaone/callback. - The application needs the monitoring, management and offline access scopes, which Tidehawk requests during authorisation.
- Know which NinjaOne region hosts your account. Your NinjaOne login URL tells you.
What Tidehawk asks for
Section titled “What Tidehawk asks for”| Field | What to enter |
|---|---|
| Client ID | The OAuth application client ID from NinjaOne |
| Client secret | The OAuth application client secret |
| Data centre region | US — Oregon and Ohio, EU — Frankfurt, Stockholm, Ireland, London, Paris, Switzerland, or OC — Sydney (Oceania) |
Connect
Section titled “Connect”- Open Integrations and select Connect on the NinjaOne card.
- Enter the Client ID and Client secret, and pick your Data centre region.
- Select Authorise with NinjaOne →. You are sent to NinjaOne to approve the request, then returned to Tidehawk.
- On Configure ticket defaults, choose a Default ticket form and select Save & finish.
- Select Test now to confirm. A working connection reports how many organisations it can see.
What a Tidehawk ticket looks like
Section titled “What a Tidehawk ticket looks like”A ticket titled SSL certificate expires in 12 days — mail.example.co.uk (Acme Ltd), or Domain expires in 12 days — example.co.uk (Acme Ltd).
The description is plain text, because the NinjaOne ticketing API takes plain text. It opens with a status line such as CRITICAL · Expires in 5 days, lists the client, the certificate or domain and the expiry date, and ends with a link back into Tidehawk.
Tickets are created with the status OPEN and the type PROBLEM, against the NinjaOne organisation whose name matches the Tidehawk client exactly. The alert’s urgency sets the severity: critical alerts become CRITICAL, high become MAJOR, normal become MINOR.
Closing
Section titled “Closing”NinjaOne tickets are not closed by Tidehawk. The adapter has no verified close path, so when the certificate or domain is renewed Tidehawk resolves its own alert, records that the provider is unsupported for closing, and leaves the ticket for you.
Tokens and expiry
Section titled “Tokens and expiry”NinjaOne issues short-lived access tokens with a refresh token. Tidehawk checks every 30 minutes for connections whose token expires within 10 minutes and refreshes them in the background.
If a refresh fails, Tidehawk retries with a growing delay, up to six attempts, capped at six hours between tries. After the sixth failure the connection is marked failed and the Integrations card shows Needs attention. Reconnect to restore ticketing.
Limitations
Section titled “Limitations”- No automatic ticket closing.
- The Default ticket form you choose is stored against the connection but is not applied when a ticket is created, so tickets use your NinjaOne default form.
- Client matching is an exact, case-insensitive name match against your organisation list, which is cached for an hour.