Integrations for facility operations data, in and out.
Webhook delivered
POST /work-orders, 200 OK
Where facility data breaks apart
"Building alarms, work orders, bookings, and approvals live in different systems"
"Residents and staff report issues from chat, QR, email, and front desks"
"ERP and finance data needs clean field mapping before it can reconcile"
"Sync errors become operational problems when no one can see what failed"
With Infodeck
APIs and webhooks move events in and out of the operating record
Messaging channels bring fault intake, tracking, and booking updates into the same flow
BMS, IoT, and identity connect through site-specific configuration
ERP, finance, and legacy systems connect through mapped data flows
Connect facility systems to one record.
Use built-in APIs and webhooks for day-to-day movement. Configure messaging and building channels around each site. Map enterprise systems when records need to reconcile cleanly.
Product-ready surfaces
Documented surfaces for moving data into and out of the operating record.
- REST API with versioned endpoints
- Event webhooks for work orders, assets, requests, and approvals
- CSV import and export across the operating record
- Google Workspace SSO
- Email and in-app notifications
Channels configured for your site
Standard protocols and channels that need tenant settings, credentials, routing rules, or device details.
- BMS and IoT protocols: BACnet, MQTT, LoRaWAN (Modbus and OPC-UA on the roadmap)
- Telegram, WhatsApp, LINE, Slack, Microsoft Teams, or SMS for fault intake, requester updates, and booking notifications
- SAML SSO providers (Azure AD, Okta, others) configured during implementation
- Scheduled CSV or SFTP sync jobs
ERP and legacy data flows
ERP, finance, and legacy systems need agreed objects, sync direction, access method, test data, and acceptance checks before they connect.
- SAP, Oracle, NetSuite, Microsoft Dynamics
- Accounting systems (Xero, QuickBooks, Sage)
- Legacy on-premises BMS, ERP, and custom middleware
- Edge computing for siloed networks and AI video analytics
work_order.created
POST https://example.com/hooks/wo
Requester update sent by channel
Fault status changed, tracking link delivered
BACnet threshold event ingested
Chiller-03 temp > 28°C, work request opened
API and webhooks
Push and pull facility data through versioned REST endpoints and event webhooks. Idempotent, paginated, and documented.
Identity and data security
TLS in transit, AES-256 at rest, Google Workspace SSO (SAML providers via implementation), permission-limited API keys, and audit log with named actor on every authenticated write.
Enterprise systems mapped clearly
SAP, Oracle, finance systems, and legacy BMS need field mapping, test data, access rules, and a handover path before they go live.
Clear integration paths for every team
Each team sees the integration path that matters to their work: APIs, channel setup, or mapped enterprise data.
Controlled connection points
Built-in API, webhooks, and SSO cover common needs. Enterprise connections define access, fields, and testing before go-live.
- Google Workspace SSO (SAML configured during implementation)
- Audit log on every authenticated write
- Permission-limited API keys
Data flowing where work happens
Webhooks push facility events to the tools your team already checks. Messaging channels support fault intake, requester tracking, and booking notifications once configured for the deployment.
- Event webhooks for work orders and approvals
- Messaging channels for intake and updates
- Custom dashboard exports via API or CSV
Cost data without copy-paste
CSV exports cover monthly close. Direct ERP sync needs mapped fields, sync direction, and test data if reconciliation needs a faster cadence.
- Cost reports via CSV or API export
- ERP sync with mapped fields
- Audit-ready trail on every export
API-first integration work
REST API with versioned endpoints, OpenAPI 3.0 spec at docs.infodeck.io, and webhook event schemas with try-it-now examples.
- OpenAPI 3.0 spec at docs.infodeck.io
- Permission-limited API keys
- Webhook retries with dead-letter queue
The integration surface, in plain terms
APIs, webhooks, CSV, SSO, messaging channels, and building-system protocols all feed the same operating record.
REST API
Versioned REST endpoints across the operating record. Pagination, idempotency, and standard error responses.
Event webhooks
Webhook events for work orders, assets, requests, approvals, and proof entries. Use them for Slack-style notifications, automation, and downstream systems.
CSV import and export
Bulk import and export for assets, locations, users, work orders, and PM schedules.
SSO
Google Workspace SSO is wired today. Azure AD, Okta, and other SAML providers are configured during implementation.
BMS, IoT, and messaging channels
BACnet, MQTT, and LoRaWAN network servers (Modbus and OPC-UA on the roadmap), plus Telegram, WhatsApp, LINE, Slack, Teams, or SMS channels for fault intake, tracking, and booking updates.
Audit log on writes
Every authenticated write is logged with actor, permission context, timestamp, and payload hash.
Integrations FAQ
How Infodeck connects APIs, messaging channels, building systems, and enterprise records.
Still have questions?
Tell us what you want to connect.
Bring the systems your team already uses. We will map the cleanest path across APIs, webhooks, messaging channels, building systems, and enterprise data.
API and webhooks are documented at docs.infodeck.io. Enterprise integrations are mapped before implementation starts.