activator-cli

Create and inspect Fabric Activator (Reflex) alert rules, sources, and actions via the Fabric REST API.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill activator-cli-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: activator-cli
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/activator-cli
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill activator-cli-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Authoring or decoding Microsoft Fabric Activator (Reflex) alerts requires assembling a complex ReflexEntities.json definition with containers, sources, rules, and actions, where small schema mistakes cause 400 errors. This Skill guides the full workflow of creating, updating, deleting, and inspecting Activator items through the Fabric REST API with correct entity wiring. ## Core Features & Use Cases - Alert Authoring: Create Activator items and rules with AttributeTrigger or EventTrigger templates, wired to Eventstream, KQL, Real-time Hub, Digital Twin Builder, or Power BI sources. - Action Binding: Attach Teams messages, emails, or Fabric item invocations (Pipelines, Notebooks, Spark jobs, Dataflows, User Data Functions) to alert rules. - Read-Only Inspection: List Activators, decode ReflexEntities.json definitions, and explain existing rules, sources, and actions without mutating anything. - Use Case: Ask to be notified on Teams when average temperature exceeds 30, and the Skill resolves the workspace, validates the source data, builds the entity graph, and persists it via updateDefinition. ## Quick Start Ask the assistant to create an Activator alert in your Fabric workspace that emails you when a KQL table column crosses a threshold.

Frequently Asked Questions about activator-cli

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

FAQPage Schema
How do I create a Fabric Activator alert with the REST API?▼

Create the item with POST /v1/workspaces/{ws}/reflexes, then persist rules, sources, and actions with POST updateDefinition carrying a Base64-encoded ReflexEntities.json. Build the payload with Python json.dumps, since PowerShell ConvertTo-Json corrupts the nested JSON strings.

How do I read an existing Activator rule definition?▼

Call getDefinition as a POST with an empty body '{}' on the reflexes endpoint, then Base64-decode the ReflexEntities.json part. A GET returns 405, and the call may return a 202 LRO that must be polled via the Location header.

What data sources can a Fabric Activator rule monitor?▼

Activator rules support Eventstream push sources, KQL database queries, Real-time Hub events, Digital Twin Builder or Ontology queries, and Power BI semantic model metrics. Each source type has its own entity schema inside ReflexEntities.json.

Why does my Activator updateDefinition call return a 400 error?▼

Common causes are raw template objects not wrapped in the entity envelope, definition.instance not stringified as JSON, missing step GUIDs, or references pointing to entities absent from the submitted array. Run a reference integrity preflight before calling updateDefinition.

Can I get Activator alert activation history from the REST API?▼

Activation history is not available via the public REST API. Use the Activator MCP server endpoint and call the get_activations_for_rule tool with the workspace ID, activator ID, and rule uniqueIdentifier.

When should I use AttributeTrigger versus EventTrigger rules?▼

Use AttributeTrigger for value-based conditions like thresholds, ranges, and aggregations, which require ScalarSelectStep and ScalarDetectStep. Use EventTrigger to fire on event occurrence, state, change, or heartbeat, using FieldsDefaultsStep and EventDetectStep with a minimal entity graph.