Hi @BalajiL ,
You’re right – there’s no native Fabric connector for Quickbase today, so you won’t get a “click-next-next-finish” style integration like you do for SQL or SaaS sources. What you can do, though, is still bring the data in using Fabric plus either Quickbase’s APIs or exports, without paying for CData if you don’t want to.
In practice, people usually do one of these:
For a one-time or rare historical load, the simplest path is: export data from Quickbase as CSV (from the UI or a basic script), drop those files into a Storage account or straight into Lakehouse Files, and then use a Fabric Data Pipeline or notebook to load them into Delta tables. For a big historical dump this is often enough, and you don’t need any extra tools.
For ongoing loads without CData, the realistic option is to sit in the middle with something that can call Quickbase’s REST APIs and then write to storage/Lakehouse. That can be:
- A small Python notebook in Fabric that calls Quickbase’s API, pulls the data, and writes it into Lakehouse tables.
- Or a Power Automate / Logic App flow using HTTP actions to call Quickbase and then write the response into a Storage container, from which Fabric pipelines pick it up.
In all of these cases, Fabric itself is only handling the “from storage into Lakehouse” part – the hop from Quickbase into storage is done via API calls or manual exports, because there isn’t a built-in connector yet.
So short answer:
Without CData or another paid connector, you’ll need a bit of custom glue (API + script/flow) to land Quickbase data into storage, and then use Fabric pipelines/notebooks to bring it into the Lakehouse. There’s no fully native “Quickbase → Fabric” connector right now.
– Gopi Krishna
