Loading...
Loading...
Found 20 Skills
Execute Code Engine functions from apps with domo.post and strict packagesMapping input/output contracts.
Query-first dataset access with @domoinc/query including filters, grouping, date grains, and performance constraints.
Convert Google AI Studio-origin apps to static Domo deployment contract.
Build and publish Domo apps with dist workflow and first-publish ID handling.
Build and publish Domo apps with dist workflow and first-publish ID handling.
Control which data each viewer sees in an embedded Domo dashboard/card via server-side programmatic filters and dataset switching. Covers the OAuth → embed token flow, standard filters, SQL filters (OR/BETWEEN/LIKE), per-dataset targeting, datasetRedirects for multi-tenant architectures, and token size limits. Use for any per-viewer, per-role, or per-tenant data restrictions at embed time. Not for client-side JS API filtering (use cap-de-jsapi-filters).
Patterns for Domo Custom Connector IDE work only (not Domo App Platform custom apps).
Apply runtime filters to embedded Domo dashboards/cards from the host page via the JS API (MessagePort). Covers dynamic filtering, drill events, filter change listeners, iframe resize, pfilter URL params, overrideFilters, and App Studio appData. Use for any client-side Domo embed interaction. Not for server-side programmatic filters (use programmatic-filters).
Orchestrates a new Domo custom app build with Remotion-compatible styling, sample data generation, and automatic demo video creation. Use when you want to build a Domo app AND produce a polished 10-15 second demo video of it in one workflow.
High-level entry skill for Domo data access. Routes detailed query work to cap-apps-dataset-query.
Use ryuu.js (domo.js) APIs for env, events, navigation, and data calls.
Magic ETL dataflows via community-domo-cli — list, get-definition, create, update, run, execution status; JSON DAG actions, transforms, joins. Use when automating dataflows with the community Domo CLI end-to-end. For REST/Java-CLI–first flows or mixed API patterns, use magic-etl instead.