Okta AED integration status
Sign-in and access. Company SSO is on the sign-in screen today, and no provider is named.
ServiceNow AED integration: no connection is confirmed
A failed inspection line adds a follow-up task in ReadyAED. ReadyAED publishes no confirmed ServiceNow connection.
ServiceNow sits in the IT and service category on this site. An IT team uses a service management platform for service requests and incidents. This page states the ReadyAED status for ServiceNow.
ReadyAED is not affiliated with, endorsed by or sponsored by ServiceNow. All marks belong to their owners. this passage needs legal sign-off
ReadyAED is an AED (automated external defibrillator) readiness and compliance platform. This page is for the IT and security team that reviews the AED program with the rest of the estate.
ReadyAED publishes no confirmed ServiceNow connection today. product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems
Use case
The AED work and the service desk, in one view.
The AED program raises work for the service desk. A failed inspection line adds a follow-up task. The task types include order pads, raise a service request, order a battery, clear an obstruction and restock a rescue kit. ReadyAED sells no hardware and no consumables. Fulfilment is by partners.
The service desk works from tickets that carry an owner and a queue. A ReadyAED follow-up task stays in the device record, so the two records have different shapes.
An IT team reads "service request" and asks a fair question: does the task open a ticket in ServiceNow? ReadyAED publishes no such connection today. product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems
The task stays in ReadyAED. The device record shows the task and the inspection that created it.
The audit trail records user and system events, device history and inspection history. A service review asks who did what and when. The activity feed shows the actor, the event and the time.
No escalation rules or channels are published. confirmation of escalation rules and channels
If your team runs ServiceNow, the open question is whether a task can reach it. ReadyAED publishes that answer only after the product team confirms it. product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems
What syncs
Follow-up tasks and the audit trail today. Nothing else is published.
| Area | What ReadyAED provides today | Status |
|---|---|---|
| Follow-up tasks | A failed checklist line adds a task in ReadyAED | Confirmed |
| Task types | Order pads, raise a service request, order a battery, clear an obstruction, restock a rescue kit | Confirmed |
| Audit trail | User and system events, device history and inspection history | Confirmed |
| Ticketing connection | Not published | product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems |
| Escalation rules and channels | Not published | confirmation of escalation rules and channels |
Follow-up tasks
The inspection screen has five checklist lines. Each line is answered Pass, Fail or N/A, and every line must be answered before the inspection is complete.
A failed line adds a follow-up task automatically. A task stays with the device record, so the next inspector sees it.
Audit trail
An audit trail records user and system events, device history and inspection history. The activity feed shows recent events with the actor, the event and the time.
Your team exports the report, a CSV (comma-separated values) file and a device history.
Device history
The device history keeps user and system events, including automatic status changes and location updates. A service review sees when a unit moved and when its status changed.
The history keeps automatic status changes, so the timeline shows when a device moved from Ready to Overdue.
Questions the review asks
- Does a failed check open a ServiceNow ticket? No connection is published. The follow-up task stays in ReadyAED. product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems
- Does ReadyAED escalate an overdue device? No escalation rules or channels are published. The app shows an alert, and ReadyAED sends email. confirmation of escalation rules and channels
- Who closes a follow-up task? The task stays with the device record. ReadyAED publishes no role or permission model. confirmed role and permission model
What is not published
- A connection that creates or updates a ServiceNow ticket. product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems
- Escalation rules and channels. confirmation of escalation rules and channels
- The role and permission model. confirmed role and permission model
API notes
No interface details are published for ServiceNow.
ReadyAED publishes no API keys, endpoints, webhooks or connection list. product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems confirmed integration list — product confirmation required
The API and integration status page states the interfaces that are confirmed today. The Security & Trust Center states the security and compliance posture.
Related integrations
The Integrations hub groups every published page by category. The other pages cover three more systems.
Workday AED integration status
People and site data. ReadyAED publishes no confirmed Workday connection today.
Slack AED integration status
Team messages. ReadyAED publishes no confirmed Slack connection today.
Book a demo.
See the inspection flow, the follow-up task and the audit trail. Bring the service-desk question your team asks. The product team confirms each interface before ReadyAED publishes it. product confirmation of REST API, webhooks and HRIS/EHS integrations, with named systems