magic-etl-cli

Create, update, and run Magic ETL dataflows in Domo via community-domo-cli.

19|13|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill magic-etl-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magic-etl-cli
Source: https://github.com/stahura/domo-ai-vibe-rules/tree/main/skills/transformation/magic-etl-cli
Command: npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill magic-etl-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Magic ETL dataflows in Domo can be created, updated, and executed entirely through the community-domo-cli. The dataflow is defined as a JSON document describing a directed acyclic graph (DAG) of actions — inputs, transforms, and outputs. This Skill enables programmatic management of data pipelines, enabling automation and repeatable deployments.

Core Features & Use Cases

  • List Magic ETL dataflows: discover existing pipelines and their configurations.
  • Get dataflow definitions: fetch complete JSON definitions for inspection or modification.
  • Create/update/run dataflows: deploy new dataflows, modify existing ones, and execute on demand.
  • Validate and manage workflow lifecycles: ensure dataflows are published and enabled for automated runs across environments.

Quick Start

Create a new Magic ETL dataflow by providing a complete JSON body to dataflows create via the community-domo-cli.

Frequently Asked Questions about magic-etl-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Magic ETL dataflow creation and execution in CI workflows?

You can automate Magic ETL dataflows in CI workflows by using the Domo CLI to programmatically list, create, update, and run dataflows defined as JSON DAGs. This enables repeatable deployments across development, staging, and production environments.

What is the JSON structure required to create a Magic ETL dataflow via the Domo CLI?

The mandatory JSON structure for creating a Magic ETL dataflow requires specifying databaseType as MAGIC. You provide this complete JSON body to the dataflows create command via the community-domo-cli.

Can I fetch and modify existing Magic ETL dataflow definitions using the CLI?

Yes, you can fetch complete JSON definitions of existing Magic ETL dataflows for inspection or modification using the Domo CLI. This allows you to retrieve dataflow configurations and update them with a full definition.

How do I validate and manage Magic ETL dataflow lifecycles across different environments?

You validate and manage Magic ETL dataflow lifecycles by ensuring dataflows are published and enabled for automated runs. The Domo CLI allows you to check executions and manage workflows across development, staging, and production.

Does the Domo CLI support running Magic ETL dataflows on demand?

Yes, the Domo CLI supports running Magic ETL dataflows on demand. You can execute dataflows directly and check their execution status to monitor pipeline runs as part of your data automation workflows.

What are the limitations of using the Domo CLI for Magic ETL automation?

The Domo CLI requires dataflows to be defined as complete JSON documents representing a directed acyclic graph of actions. Dataflows must be properly published and enabled for automated runs to execute successfully across environments.