Skip to main content

Slack and Microsoft Teams alerts

OnTrackio can push notifications to a Slack or Microsoft Teams channel through an incoming webhook, so your IT team sees new requests and equipment transfers without logging in. Each connector is one POST-able URL per channel that you paste into Settings, then verify with a test message.

:::note Before you begin

  • You're signed in to your workspace as an admin (admin, it-admin, or super-admin). See Logging in.
  • You can create an incoming webhook in the target Slack workspace or Teams channel. This usually needs Slack workspace-app rights, or permission to add a Workflow in the Teams channel.
  • The webhook destination must be a public https URL. OnTrackio refuses URLs that resolve to a private, loopback, or link-local address. :::

How alerts work

Both connectors share the same shape: OnTrackio POSTs a short JSON message to the webhook URL you save. There's no token exchange, no OAuth, and the channel is fixed on the chat platform's side when you create the webhook.

ConceptSlackMicrosoft Teams
Connector typeIncoming WebhookWorkflows webhook (Post to a channel when a webhook request is received)
Message formatPlain Slack text with an Open in ITAM linkAdaptiveCard (version 1.4)
ChannelFixed by the webhookFixed by the workflow
URL storedEncrypted at restEncrypted at rest
AuthenticationNone — the URL is the secretNone — the URL is the secret

:::warning Live alerts currently flow to Slack only The Test connection button works for both connectors, and OnTrackio saves and encrypts the Teams webhook. But event-driven alerts (new request, transfer, and the events below) are delivered to the Slack webhook today. Save and test the Teams webhook to confirm the channel is reachable, but don't rely on it for live notifications yet. :::

What triggers an alert

When Slack alerts are enabled, OnTrackio posts to the channel on these events. The message carries the subject, a short body, and an Open in ITAM deep link back to the record.

EventFires when
asset_request_approvedAn admin approves a request
asset_request_rejectedAn admin declines a request
asset_request_fulfilledA requested item is handed over
asset_request_replySomeone posts a message on a request
hardware_assignedA device is assigned to a user
warranty_expiringA device's warranty nears its end
license_expiring / license_renewal_dueA software license approaches renewal
transfer_agreement_issuedA transfer agreement is issued
pool_checkout_dueA loaner is due back

Connect Slack

To post alerts to Slack, create an incoming webhook, then save and test it.

  1. In Slack, open api.slack.com/apps and create (or pick) an app in your workspace.
  2. Enable Incoming Webhooks, add a webhook to the channel you want, and copy the generated URL. It looks like https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXX.
  3. In OnTrackio, go to Admin → Settings, open the Integrations tab, and select the Slack card.
  4. Select Enable Slack notifications.
  5. Paste the URL into Webhook URL.
  6. Select Save at the bottom of the Settings page.
note

Save before you test. The Test connection button reads the webhook from saved settings, not from the field you just edited. If you test without saving, OnTrackio tests the previously stored value (or none).

  1. Reopen the Slack card and select Test connection.
  2. Check the channel for a webhook test message. The card shows Test message delivered to Slack. Check the channel. on success.

The card's status badge reads Connected once both the toggle is on and a webhook URL is saved.

Connect Microsoft Teams

Teams uses a channel Workflow rather than the retired Office 365 connector. To set it up:

  1. In the target Teams channel, select (more options) → Workflows.
  2. Choose Post to a channel when a webhook request is received and complete the wizard.
  3. Copy the generated workflow URL. It looks like https://prod-XX.westeurope.logic.azure.com:443/workflows/.../triggers/manual/paths/invoke?....
  4. In OnTrackio, go to Admin → Settings → Integrations and select the Microsoft Teams card.
  5. Select Enable Microsoft Teams notifications.
  6. Paste the URL into Webhook URL.
  7. Select Save.
  8. Reopen the Microsoft Teams card and select Test connection to POST a test AdaptiveCard to the channel.
tip

Use the Workflows-flavoured webhook. The classic Office 365 / Incoming Webhook connectors are being retired by Microsoft, so a Workflows URL is the durable choice.

Settings reference

Both connectors live on the Integrations tab and are saved by the single Save action on the Settings page.

FieldConnectorRequiredDefaultNotes
Enable Slack notificationsSlackNoOffMaster switch for live Slack alerts. Off means no events are posted, even with a saved URL.
Webhook URL (Slack)SlackWhen enabledEmptySlack incoming-webhook URL. Encrypted at rest. The channel is fixed by the webhook.
Enable Microsoft Teams notificationsTeamsNoOffSaves the toggle. See the note above on live-alert delivery.
Webhook URL (Teams)TeamsTo testEmptyTeams Workflows webhook URL. Encrypted at rest.

A card's Connected badge requires both the connector's toggle on and a non-empty webhook URL. With either missing, the badge reads Not connected.

Per-user delivery

Channel alerts are an organization-wide setting you control here. Individual users can't add their own webhook, but they manage their own email notifications and read everything in the in-app inbox.

Verify

  • The connector card shows a Connected badge after you enable the toggle, save a webhook URL, and reload the Settings page.
  • Test connection returns Test message delivered to <platform>. Check the channel. and the test message appears in the channel within a few seconds.
  • After an approval or transfer, a matching alert with an Open in ITAM link appears in the connected Slack channel.

Troubleshooting

SymptomWhat to do
No <platform> webhook URL is saved. Paste it above, click Save, then retry.Paste the webhook into Webhook URL and select Save before testing. The test reads the saved value, not the in-progress field.
<platform> rejected the test: HTTP 4xx — <reason>The webhook is reachable but refused the message. Slack returns a reason such as no_service or invalid_payload; recreate the webhook and paste the fresh URL.
Could not reach <platform>: ...OnTrackio couldn't connect within 8 seconds. Confirm the URL is current and the workspace or channel still exists.
Outbound URL resolves to a private/loopback/link-local address. or Outbound URL to localhost is blocked.The URL points at an internal or metadata host and is blocked for safety. Use the public https webhook the chat platform generated.
Test passes but no live alerts arrive in TeamsExpected for now — live event alerts are delivered to Slack only. See the note under How alerts work.
Slack test passes but events never postConfirm Enable Slack notifications is on and saved. The toggle gates every live alert independently of the webhook URL.
A test message looks wrong or arrives in the wrong channelThe channel is fixed when you create the webhook. To change it, create a new webhook for the right channel and paste that URL.