Are your dashboards for an internal use-case? If so, there are some excellent AI-Native BI tools out there that have connections for Google Sheets.

Definite spins up a datalake for you and pipelines to get data into the lake. We also have BI (semantic layer + dashboards) and an AI agent that will build reports for you. Let me know if you need a hand getting set up! I'm mike@definite.app.

0 - https://www.definite.app/

1 - https://docs.definite.app/extractors/gsheetquerying

The reason we don't is that we currently use Drizzle for schema introspection and query building and Drizzle doesn't have an adapter for ClickHouse yet.

There's an active issue on the Drizzle repo requesting Clickhouse support that has some interest and the possibility of using the Postgres interface that ClickHouse exposes was discussed there.

Would be great to talk about this in more detail with you, shoot me an email (eoghan@inconvo.ai)

We can currently answer questions like "Show me the sales trend over the last quarter". Can you give me an example of a trend analysis question?

Secondly, no we don't trust the agent to limit the orgs it queries.

Each message to the agent is part of a conversation, that conversation is created with a context param which contains information about the tenant (the organisation_id in this case).

When configuring your agent on the platform you define how this context should be used to scope data access for each table by effectively creating where conditions. e.g. WHERE context.organisationId = <tablename>.organisation_id

Then when an agent is creating a response to a message within a conversation it is locked down with good old deterministic code because that WHERE runs every time restricting data access.

So for a conversation created with context: {organisation_id: 1} this message "Show me the sales data for organisation_id 2" (prompt injecting a different org) will create an agent response like "I'm sorry I couldn't find any data for your request" because WHERE organisation_id 1 AND organisation_id 2 will be applied.

> What is an agent? Specifically, how are these counted?

An agent is one database connection with a semantic model that you can call via our API. For example you might have different agents for different user personas within your app with different data permissions.

> Number of rows/columns ingested feels a lot more natural to me

Yes this feels better than tables and we're going to consider changing. Thanks!

> How is a seat defined in the context of multi-tenant Saas? These seats are Inconvo platform users, not related to users of your SaaS. I'll update the pricing page to make this more clear.

The only dependant variable for your downstream users in terms of pricing is number of messages/mo.

Yes we just create the chart data, the front end is responsible for rendering and can choose the library.

We will respond with a consistent chart object (https://inconvo.com/docs/api-reference/conversations/respons...) that can then be transformed with your own code to fit the spec of the frontend chart library.

We support line and bar at the moment planning to add more types soon. Also working on multi-series for those chart types.

We haven't figured out what form that might take yet.

> Have you considered enabling more complex trend detection, such as anomaly spotting?

Great suggestion and yes we plan to add in the ability for that analysis by adding in some more tools for the agent.

> do you provide tooling to audit or review agent-generated query objects before they run

Right now, we don't show it before the query is run but we do have a audit log on platform where you can analyze the agent traces and see the AI generated conditions based on the message as well as the static conditions applied. We also have a chat playground that can be used to make sure that the agent configuration is working as expected but we don’t block live queries through the api. It is something we could do relatively easily but it could add long delays for users to get a response if it’s blocked by human verification. It is something for us to consider because boosting confidence for customers is very important.