metabase-data-app-actions

Call the useAction hook from @metabase/embedding-sdk-react with the action's numeric id from the schema, then invoke execute with a parameters object keyed by parameter slug. Actions only run when execute is called explicitly, never on mount.

Pass ActionParametersFromDataAppSchema and ActionKindFromDataAppSchema generics from @metabase/embedding-sdk-react/data-app to useAction. The helpers expand the schema's parameters list into a keyed object with required flags and jsType-based value types.

Actions do not automatically refresh on-screen data. After execute resolves, you must call and await the refresh callbacks of every data view reading the mutated model, ideally with Promise.all when multiple refreshes apply.

Read error.data.message for whole-request failures and error.data.errors keyed by parameter slug for per-field validation messages. Render them verbatim in an element with white-space pre-wrap since driver messages contain meaningful newlines.

No. The data app sandbox blocks raw network calls to the Metabase origin; fetch and XHR only work for external allowed_hosts declared in data_app.yaml. The only path to actions is the useAction hook.

Only the required flag from the schema's parameter entries, wired to native input required attributes and checked via form checkValidity. Do not add length, format, or min/max checks; anything beyond required comes back as a backend error after submit.