Introducing Notehub IQ: Use AI to Talk to Your Products

Ask questions about your deployed products in plain language and get answers from the data you already collect, through Notehub MCP, with no pipeline to build.


Read the full blog post at https://blues.dev/blog/introducing-notehub-iq and continue the discussion here.

Hey we are having trouble accessing our custom notefiles, we have a data.qo notefile which is a custom file that we upload from our devices and the mcp client can list it as a file but when creating a repo it isnt populating the dataset at all but the session.qo files are sending all the data and populating all the fields.

Thanks for reaching out. It looks like the dataset got created with a time field that didn’t exist on your events. Usually we use the “when” field which is the time at which the event was created, but for your events that field is always empty. I think this is an onboarding hiccup that we need to address.

I recreated your dataset this time with a proper time field (the uploaded time) and it looks like it’s populated now. Let us know if you see any other issues. It seems like you’ve also included the timestamp as an additional field from your event body, and that value is still present in the dataset.

Thanks,

Scott Frazer

Thank you very much for the help, and your reply, it works now.
Edit:
Made a new dataset, stopped working again

Hey Scott, As soon as we dropped the table, to work on a full repository instead of testing one, the issue reoccured, are we advised not to drop the dataset in this case.

Yes I saw that the dataset got re-created again with an invalid time field, which was causing all of the records to be dropped again.

We are currently working on a more robust fix for this, but in the mean time you can perhaps try to tell the LLM to use event.body.t as the time field