skills.rest
rbutinar
rbutinarCOMMUNITY
Explore all skills by this author →
Website𝕏@rbutinarGitHub

fabric-pipeline-run

Trigger Microsoft Fabric Data Pipeline runs and return run IDs.

Updated May 26, 2026
Search Tags:#fabric#databricks#data automation#pipeline execution#fabric pipeline
One-click install
npx skills add https://github.com/rbutinar/ade-ops --skill fabric-pipeline-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fabric-pipeline-run
Source: https://github.com/rbutinar/ade-ops/tree/main/.agents/skills/fabric-pipeline-run
Command: npx skills add https://github.com/rbutinar/ade-ops --skill fabric-pipeline-run

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires FabricConnector, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for a streamlined and automated execution of Microsoft Fabric Data Pipelines, providing a seamless experience for on-demand runs and ensuring efficient processing.

Core Features & Use Cases

  • On-Demand Pipeline Execution: Trigger runs of Data Pipelines as needed, returning immediate feedback on the run_id for asynchronous execution.
  • Integration with Deployment and Polling Skills: Complements /fabric-pipeline-deploy for verification and /fabric-pipeline-poll for status tracking.
  • Use Case: Ideal for validating pipeline functionality, re-running failed pipelines after corrections, or incorporating into CI/CD pipelines.

Quick Start

Execute a Fabric Data Pipeline by providing the pipeline ID and environment: /fabric-pipeline-run --pipeline-id <id> --env dev

Frequently Asked Questions about fabric-pipeline-run

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

FAQPage Schema
How do I trigger a Microsoft Fabric Data Pipeline on demand?▼

To trigger a Microsoft Fabric Data Pipeline on demand, you execute a command providing the pipeline ID and environment. This automates the pipeline run, returning an immediate run ID for asynchronous execution tracking.

What do I need to execute Fabric Data Pipelines using automation?▼

Executing Fabric Data Pipelines requires FabricConnector credentials and a previously deployed pipeline. You must also specify the target environment, such as dev, and the specific pipeline ID to initiate the run.

Can I use this to re-run failed Databricks or Fabric pipelines?▼

Yes, you can use this to re-run failed Databricks or Fabric pipelines. It triggers on-demand pipeline execution, which is ideal for validating pipeline functionality after making corrections to previous failures.

How does asynchronous processing work for Fabric pipeline execution?▼

Asynchronous processing for Fabric pipeline execution works by triggering the run and immediately returning a unique run ID. This allows you to continue other tasks without waiting for the pipeline to complete.

What is the best way to track the status of a triggered Fabric pipeline run?▼

The best way to track a triggered Fabric pipeline run is by using a complementary polling skill. The run ID returned during execution can be used to monitor status and verify completion alongside deployment skills.

Related Skills

Explore More Software Engineering Skills→
rbutinarrbutinar

fabric-notebook-deploy

Deploy Databricks-style notebooks to Microsoft Fabric workspaces with validation.

Community
Intermediate
HaykTarkhanyanHaykTarkhanyan

deploy-watch

Monitor CI deployment runs after a push and report final status.

Community
Advanced
rbutinarrbutinar

migration-assess

Automate Databricks to Fabric migration with compatibility assessment and lakehouse provisioning.

Community
Advanced
mathruffian-dotmathruffian-dot
70

codex-firebase

Connects Codex to Firebase for data synchronization and service integration.

Community
Basic