Einführung
When a Level alert fires, this integration opens a ticket in DeskDay automatically. Nein manual hand-off. Setup takes about 10 minutes and spans both platforms: you'll create an API key and webhook in Level, then finish the configuration on the DeskDay side.
ℹ️ HINWEIS: This integration was built and is maintained by the DeskDay team. For full DeskDay-side setup details, see their documentation: How to Integrate with Level RMM.
⚙️ PREREQUISITES
Level administrator access (required to create API keys and webhooks)
DeskDay account with Integrationen permission
🎬 VIDEO
DeskDay Integration
Erstellen an API Key in Level
Level needs an API key so DeskDay can authenticate requests on your behalf.
In Level, navigate to Einstellungen → API Keys.
Klicken Sie auf Erstellen Key.
Give it a descriptive name (for example, "DeskDay Integration") and click Speichern.
Copy the generated API key. You'll paste this into DeskDay in the next section.
Konfigurieren the Webhook in Level
Once you've initiated the connection in DeskDay, it generates a Webhook URL and Secret ID. Bring those values back to Level.
In Level, navigate to Einstellungen → Webhooks.
Klicken Sie auf Erstellen Webhook.
Geben Sie ein a name (for example, "DeskDay Warnungen") and paste the Webhook URL from DeskDay into the URL field.
Paste the Secret ID into the Secret field. This authenticates DeskDay's incoming requests.
Under Events, select Alert Erstellend and any other alert event types you want forwarded.
Klicken Sie auf Speichern.
Finish Setup on the DeskDay Side
Return to DeskDay and click Proceed. DeskDay validates the API key and webhook you just configured.
Once the connection is confirmed:
Wählen which DeskDay board will receive Level alerts as tickets.
Optionally map customers and devices so each ticket is tagged to the right client automatically.
Test the Integration
In Level, trigger a test alert — for example, generate a synthetic CPU threshold breach.
Confirm a new ticket appears in your chosen DeskDay board with the correct customer and device information.
If the ticket doesn't appear:
Verify the API key in DeskDay matches exactly (no extra spaces).
Check the Webhook URL and Secret in Level for typos.
Review webhook delivery logs at Einstellungen → Webhooks → [your webhook] → Ansicht Logs and look for non-200 HTTP response codes.
Ongoing Management
Rotate your API key periodically at Einstellungen → API Keys → Regenerate.
To stop forwarding alerts, disable or delete the webhook at Einstellungen → Webhooks.
To remap customers or devices in DeskDay, go to Control Center → Integrationen → Level in your DeskDay account.
Häufig gestellte Fragen
Who needs to set this up? A Level administrator (for API keys and webhooks) and a DeskDay user with Integrationen permission. Both sides need to be configured before the integration works.
Do I need to configure anything in DeskDay first? Ja. Start in DeskDay by clicking Connect on the Level integration. DeskDay generates the Webhook URL and Secret ID you'll need to complete the Level side of the setup.
Which alert events can I forward to DeskDay? Any alert event that Level supports via webhooks — at minimum, select Alert Erstellend. You can also add alert-resolved events if DeskDay supports auto-closing tickets.
What if tickets stop appearing after working for a while? Check Einstellungen → Webhooks → Ansicht Logs in Level for delivery errors. A rotated or deleted API key, or a changed webhook URL on the DeskDay side, are the most common causes.
Can I map specific devices or groups to specific DeskDay boards? Customer and device mapping is configured in DeskDay after the initial connection. See DeskDay's documentation for mapping options.