Use case
IoT Data Integration with Your ERP and CRM
Connected-device businesses collect data on a platform of their own, then sell, invoice and support from an ERP and a CRM. Rapidi joins those business systems, and reads the data your platform already keeps in a database or behind a REST API.
Where Rapidi fits
Rapidi works one step up from the devices.
Rapidi has no connector for devices or sensors. It connects to the systems where that data lands: an SQL database, a REST API or an OData service. From there, transfers are configured on screen and run on a schedule, into and out of your ERP and CRM.
That makes it a fit for the business side of an IoT company: the customers, orders, invoices and records that have to agree across systems.
Who it suits
- Your platform stores its data in an SQL database or exposes it through a REST API, and your ERP or CRM needs some of it.
- Sales works in the CRM while orders and invoices sit in the ERP, and the two do not agree.
- Your team copies records from the platform into the ERP or CRM by hand.
- The database sits on your own network, and you do not want to open inbound ports.
- You want one integration platform for your business systems, not a custom script per system.
How Rapidi reaches your data
Generic connections for the places a device platform usually keeps its data.
REST Web Service
Both ways, for any REST-based service. Rapidi learns the objects and fields from a JSON Schema or Swagger 2.0 description. Paged reads handle large data sets, and Source Control asks the service only for records newer than the last one read.
SQL databases
Microsoft SQL Server, MySQL, Oracle, IBM DB2, SQLite and Google BigQuery. A table can be the source or the target of a transfer.
OData
For systems that publish an OData service. It is a generic connection and cannot be guaranteed to work with every system, so ask us about yours first.
ERP and CRM
Dynamics 365 Business Central, Finance and Operations, NAV, GP, C5 and Oracle NetSuite on the ERP side. Salesforce, Dynamics 365 Sales and HubSpot on the CRM side.
What you get out of it
No re-keying
Transfers run on their own, so nobody types a record from the platform into the ERP or CRM again.
Only what changed
On a REST source, Source Control returns only the records newer than the last read, so each run moves the new data.
Your network stays closed
The RapidiConnector sits inside your network and uses one outbound port, with no fixed IP addresses and no inbound ports to open. Traffic is encrypted with TLS 1.2 or 1.3.
Configuration, not code
Field mapping, conversions, filters and rules are set up in the interface, so a new field does not become a development project.
Three steps, no developer
- Connect. Choose the systems you want to integrate.
- Configure. Set up the transfers on screen, field by field.
- Sync. Data moves automatically, in real time or on the schedule you set.
What that looks like in practice
idem telematics builds telematics systems for transport and logistics companies, with gateways in around 50,000 trailers. Its product moves data from a moving vehicle to a back office in real time. Its own sales team worked in Salesforce while the business ran on Microsoft Dynamics NAV, and struggled to find out what a customer had bought. Rapidi connected Salesforce to Dynamics NAV in about two weeks. The integration joins the CRM and the ERP, not the device data.
In their own words
What customers say
“We are a satisfied user of Rapidi. Our past sales data and statistics are always up to date so our team can concentrate on selling. They are no longer struggling to get the data they need.”
Internal and international sales, idem telematics
Frequently asked questions
Does Rapidi connect directly to IoT devices or sensors?
No. Rapidi has no connector for devices or sensors. It connects to the SQL database, REST API or OData service where your platform stores the data, and moves it to and from your ERP and CRM.
Can Rapidi read data from our platform's REST API?
Usually, if the service has a REST API. The REST Web Service connection moves data both ways and learns the objects and fields from a JSON Schema or Swagger 2.0 description. There is no single REST standard, so some services need extra setup.
Can Rapidi move only new records?
Yes, on a REST source. The field named in Source Control is added to each request with the last value Rapidi read, so the service returns only newer records.
Our data sits in a database on our own network. Can Rapidi reach it?
Yes. The RapidiConnector sits inside your network and uses one outbound port, with no fixed IP addresses and no inbound ports to open. Traffic is encrypted with TLS 1.2 or 1.3.
How often does the data move?
On a schedule you set. The shortest interval depends on your plan, from one hour on Entry down to one minute on Unlimited.
What does it cost?
Rapidi is priced per subscription plan rather than per connector, so adding a connection does not change the licence.
Last reviewed: 17 September 2026.
Where does your device data land?
Tell us which database or API holds it, and which ERP and CRM need it, and we will tell you plainly whether a Rapidi connection covers it.