Telemetry ingestion
Receive and normalize events from connected devices.
CONNECTOR CATEGORY
IoT Connectors for SaaS products
Connect your SaaS product with connected device, telemetry and IoT applications to turn device signals into reliable product, service and operational workflows.
Event-driven action
Trigger service, notification and data workflows from device conditions.
Device context
Associate readings and alerts with the correct customer and asset.
Governed commands
Restrict device actions and credentials by tenant and use case.
CATEGORY OVERVIEW
Build connectivity with IoT Connectors
Cyclr’s IoT Connectors help SaaS teams embed customer-facing integrations with connected device, telemetry and IoT applications. Use reusable workflows to turn device signals into reliable product, service and operational workflows, while Cyclr manages customer authentication, tenant-specific configuration and the Connector layer behind the experience.
FEATURED CONNECTORS
Featured IoT Connectors
Start with some of the most useful IoT Connectors for customer-facing integrations.
Twilio Sync
Synchronize web and mobile apps with a single source of state in... Read Article
View Connector →
Generic Webhook
Connect to any form with our Webhook connector
View Connector →
DataDog
Datadog is a monitoring service for cloud-scale applications, providing monitoring of servers,... Read Article
View Connector →CONNECTOR LIBRARY
Explore all IoT Connectors
2 Connectors are available.
Any Other Application
Our library is ever growing. However, our team can accelerate the development... Read Article
View Connector →
Wattsense
The new standard in building connectivity. Wattsense is a non-intrusive building connectivity... Read Article
View Connector →No matching Connectors found
Try another search or ask Cyclr about the Connector you need.
INTEGRATION USE CASES
What your users can do with these integrations
Create service work from alerts
Connect device threshold alert activity with a reusable IoT integration workflow.
- Source: Device threshold alert
- Workflow: Enrich the event with asset context and create the service task
- Outcome: Teams respond with the information they need
Store telemetry for analysis
Connect new sensor readings activity with a reusable IoT integration workflow.
- Source: New sensor readings
- Workflow: Normalize timestamps and units before loading the approved dataset
- Outcome: Customers can analyze consistent device data
Notify customers about device state
Connect meaningful device change activity with a reusable IoT integration workflow.
- Source: Meaningful device change
- Workflow: Apply routing and communication rules for the active tenant
- Outcome: Users receive timely, relevant updates
AI INTEROPERABILITY
Use IoT Connectors with AI agents and MCP
Use Cyclr's IoT Connectors to make selected device, telemetry event, sensor reading data and actions available to AI agents through governed MCP tools. Cyclr keeps authentication customer-specific, limits the methods each agent can use and can run reusable workflows before returning concise, grounded results.
COMMON QUESTIONS
IoT Connector FAQs
IoT Connectors are packaged integrations between a SaaS product and connected device, telemetry and IoT applications. With Cyclr, product teams can expose customer-facing workflows without building and maintaining every external API connection themselves.
Common data includes Device, Telemetry event, Sensor reading, Alert and command. The exact objects and methods depend on the connected application and the permissions granted by each customer.
Typical uses include create service work from alerts, store telemetry for analysis and notify customers about device state. Cyclr lets teams package these as reusable, tenant-aware workflows inside their own product experience.
Yes. Selected Connector methods can be exposed as governed MCP tools so an agent can check current device state. Cyclr manages customer-specific authentication and allows product teams to validate, minimize and orchestrate data before it reaches the model.
KEEP EXPLORING