activator-authoring-cli

Create and manage Fabric Activator alerts and rules via REST API and az CLI.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill activator-authoring-cli-9vantage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: activator-authoring-cli
Source: https://github.com/9vantage/skills-for-fabric-clone/tree/main/plugins/fabric-authoring/skills/activator-authoring-cli
Command: npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill activator-authoring-cli-9vantage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up alerts, notifications, and automated actions on Microsoft Fabric data requires hand-crafting complex ReflexEntities.json definitions with nested entity graphs, stringified templates, and Base64-encoded payloads, which is error-prone and poorly documented. ## Core Features & Use Cases - Activator Item CRUD: Create, update, and delete Reflex items through the Fabric /reflexes REST API using az rest with correct token audience and LRO polling. - Rule Authoring: Build AttributeTrigger and EventTrigger rule templates with detection conditions, aggregations, occurrence options, and dimensional filters. - Multi-Source Support: Connect rules to Eventstream, KQL/Eventhouse, Real-time Hub, and Digital Twin Builder / Ontology sources. - Action Bindings: Wire Teams messages, emails, and Fabric item invocations (Pipelines, Notebooks, Spark jobs, Dataflows, UDFs) to rule triggers. - Use Case: A user asks to be notified on Teams when sensor temperature exceeds 30 degrees; the skill resolves the workspace and KQL database, validates the query, assembles the entity graph, and publishes a running alert rule. ## Quick Start Ask the assistant to create an alert that sends you a Teams message when a value in your Fabric Eventhouse table crosses a threshold.

Frequently Asked Questions about activator-authoring-cli

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

FAQPage Schema
How do I create an alert in Microsoft Fabric Activator using the REST API?

Create a Reflex item via POST to /v1/workspaces/{workspaceId}/reflexes, then build a ReflexEntities.json definition containing a container, source, SourceEvent view, and rule entity, and upload it with updateDefinition. The payload must be Base64-encoded and rule templates must be JSON-stringified inside definition.instance.

What is the difference between AttributeTrigger and EventTrigger in Activator rules?

AttributeTrigger monitors attribute values using ScalarSelectStep and ScalarDetectStep for thresholds, ranges, and aggregations. EventTrigger fires on event occurrence using FieldsDefaultsStep and EventDetectStep, supporting state, change, and heartbeat detection without attribute modeling.

Can Activator rules run a Fabric pipeline or notebook when a condition is met?

Yes, use a standalone fabricItemAction-v1 entity referencing the target item, then bind it in the rule's ActStep with a FabricItemBinding row of kind FabricItemInvocation. Supported targets include Pipelines, SynapseNotebooks, SparkJobDefinitions, Dataflows, and User Data Functions.

Why does updateDefinition fail with an invalid definition error for Activator?

Common causes include outputting a raw rule template instead of the full timeSeriesView-v1 entity envelope, forgetting to JSON-stringify definition.instance, missing step IDs, duplicate GUIDs, or using PowerShell's ConvertTo-Json which corrupts nested JSON strings. Use Python's json.dumps to build payloads.

Should I filter data in the KQL query or in the Activator rule?

Filter in the rule, not the KQL query. The KQL source should return all relevant data for the time window; thresholds, text conditions, and dimensional filters belong in the rule's detection steps so the alert logic stays configurable.