Product

Workflows

A notebook builder with connector, SQL, Python, and save-to-database cells—for the questions that don't fit a dashboard, right inside InfiniStack.

A real notebook, next to your pipelines

Dashboards answer the questions you planned for. Workflows are for the ones you didn't—a mix of SQL and Python in one notebook, running directly against a database you connect.

Connect a database, chain cells together, iterate on a query, reshape the result in Python, and write it back to a table—all in one notebook, with no notebook server for you to set up or manage.

Cell types
Connector, SQL, Python, Save
Execution
Against a database you connect
Output
Dataframes & saved tables
Access
Org-scoped, role-based

From question to answer, in one notebook

Every workflow is a sequence of cells you can run, edit, and re-run—each one building on the last.

Step 1

Connect and query with SQL cells

Pick one of your organization's database connectors, or define a connection in a connector cell, then write and run SQL against it. Browse tables and columns in the schema panel, get query suggestions from the built-in AI SQL assistant, and inspect every result as a table inline.

Step 2

Transform with Python cells

Use a SQL result in a Python cell as a dataframe to reshape, join, or model it—earlier results are available by variable name, with nothing to export.

Pandas dataframes Named variables between cells
Step 3

Save back to your database

Write a dataframe to a new or existing table in a database you choose, with a setting for what to do if the table already exists. Add markdown cells along the way to document what the notebook does.

Every cell type you need, none you don't

SQL cells

SQL against a connected database, with a schema browser, an AI SQL assistant, and inline result tables. Optional incremental fetch for large tables.

Python cells

Reshape, model, or script pandas dataframes from earlier cells in the same notebook.

Save-to-database cells

Write a dataframe to a new or existing table in a database you choose.

Connector cells

Choose an organization database connector, or define a connection, that later cells query or write to.

Markdown cells

Document what the notebook does, right alongside the code.

Beyond the notebook: schedule, version, monitor

A workflow isn't just something you run by hand—it can run on a schedule, with every change and every run on record.

Scheduling

Attach a cron schedule to a workflow, or hit Run All whenever you need it.

Versions

Save your draft as a version and activate it. Runs use the active version, not your work in progress.

Run history & logs

See every run with its status, which version produced it, and per-cell logs. In-flight runs can be cancelled.

Incremental fetch

Optionally have a SQL cell pull large tables in batches, picking up where the last run stopped.

Common questions

Do I need to export data to use a workflow?

No. SQL cells query the database you connect directly, and Python cells work on those results as dataframes—there's no separate export or upload step to run a notebook.

Can I pass a SQL result into a Python cell?

Yes. Any cell's output is available to the cells that follow it in the same notebook, so a SQL query's result becomes a dataframe you can work with directly in a Python cell.

Where does a save-to-database cell write to?

Into a new or existing table in a database you choose—an existing connection or one you define in the notebook—with options for what to do if the table already exists.

Can a workflow run on a schedule?

Yes. Attach a cron schedule to a workflow and it runs automatically, using its active saved version. You can also run all cells manually at any time and review every run, with per-cell logs, in the run history.

Who can see a workflow I create?

Workflows are scoped to your organization and available to roles that manage data, such as integrators and admins—regular members don't see them. See Security for the full model.

Open a notebook on your own data

Connect a source, write a query, and save the result back—without leaving InfiniStack.