Skip to main content
Arcanflows

Data & Actions

Bind components to data and wire buttons/forms to agents, workflows, and records

An App is only useful when its components show live data and its buttons do something. This page covers data binding, actions, and publishing.

Data binding

Data-bound components (tables, stat cards, charts) read from a data source — most often one of your Data Tables:

  • A Data Table component shows records from a table; apply filters and choose columns.
  • A Stat Card computes a single value (count, sum, latest) from a table.
  • A Chart aggregates records over a field.

Because these read live data, the App updates as your underlying records change — no manual refresh of static content.

Actions

Buttons and forms can trigger real work:

  • Run an agent — send input to an agent and show/store its response.
  • Run a workflow — kick off an automation with the App's data.
  • Record operations — create, update, or delete records in a Data Table.

This is what turns an App from a read-only dashboard into an interactive tool: a button that files a ticket, a form that runs an agent and saves the result, an action that updates a status.

Forms in Apps

A Form component captures input and writes it — into a Data Table, into a workflow, or as an agent prompt. Combine a form (intake) with a table (results) on one page for a complete mini-application.

Publishing & embedding

When the App is ready:

  • Publish it for your team to use inside the console.
  • Embed it where customers need it, as a branded self-service surface.

Putting it together

A typical App: a table of records, stat cards summarizing them, a form to add new ones, and buttons that run an agent or workflow on a selected record — all bound to a single Data Table, themed to your brand, and published.

Related