Apps
Apps connect your workspace to other tools without writing code. Install them under Settings → Apps → Marketplace; each installation runs on the events you pick and is listed under Installed apps with its delivery log.
| App | What it does | Direction |
|---|---|---|
| Slack | Ticket events in a channel, threads, buttons, /stoneity | Both |
| Microsoft Teams | Ticket events as Adaptive Cards, buttons, chat commands | Both |
| Jira Cloud | Issue per ticket, comment and status sync | Both |
| GitHub | Pull requests and commits linked to tickets | GitHub → Stoneity |
| WhatsApp Business | Conversations become tickets, replies go back | Both |
| Zapier | Thousands of apps through webhooks and the Public API | Both |
Outbound deliveries
Every app shares the runtime used by webhooks: deliveries are retried on the same schedule, and an app is set to Error after 20 consecutive failures, which notifies workspace administrators. Failures that cannot succeed on a retry (a wrong channel, a revoked token, a missing Jira permission) are not retried at all.
Inbound requests
Apps that receive data get a private inbound address when you install them, shown under Installed apps → Settings:
https://api.stoneity.com/public/v1/inbound/<app>/<token>The token identifies the installation, and each app additionally verifies the sender's signature. Treat the address as a secret. It stops working the moment the app is uninstalled, and rotating it means uninstalling and installing again.
Inbound requests appear in the same delivery log as outgoing ones, marked In, so you can see what a provider sent and what Stoneity did with it.
Acting on your behalf
An app that changes tickets from the outside (a Slack button, a Jira comment coming back) acts as its own service account, so the history shows which app made the change. When the person clicking has a Stoneity account with the same e-mail address as their Slack or Teams account, the change is recorded under their name instead, and their permissions apply.