When event is triggered in Ubidots, sync it to Firebase / Firestore.
When an event is triggered in Ubidots, push the event payload into a Firebase / Firestore database collection.
See all Ubidots + Firebase / Firestore integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Ubidots Explore Ubidots →
TriggersFires when a device connected to Ubidots comes online.
Fires when a device connected to Ubidots goes offline.
Fires when a reading from a device in Ubidots crosses a set threshold.
Sends a control command to a device via Ubidots.
Adds a new device to Ubidots.
Records a sensor reading or event from Ubidots.
Firebase / Firestore Explore Firebase / Firestore →
TriggersFires when a new row is added to a table in Firebase / Firestore.
Fires when an existing row changes in Firebase / Firestore.
Fires when a scheduled query in Firebase / Firestore finishes running.
Runs a SQL query against Firebase / Firestore and returns the result.
Writes a new or updated row to Firebase / Firestore.
Syncs a table in Firebase / Firestore with data from another source.
Common questions
Can Knit build “When event is triggered in Ubidots, sync it to Firebase / Firestore.” between Ubidots and Firebase / Firestore?
Yes — describe it in the box above and Knit's Integrations Agent researches Ubidots and Firebase / Firestore's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.