activator-authoring-cli

Create Microsoft Fabric Activator definitions for alerts, notifications, and automated actions.

3|6|Updated Jun 21, 2024

Search Tags:#automation #alerts #reflex #kql #eventstream #microsoft fabric #activator

Ready to run

npx skills add https://github.com/rritec/Microsoft-Fabric --skill activator-authoring-cli-rritec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: activator-authoring-cli
Source: https://github.com/rritec/Microsoft-Fabric/tree/main/skills/plugins/fabric-authoring/skills/activator-authoring-cli
Command: npx skills add https://github.com/rritec/Microsoft-Fabric --skill activator-authoring-cli-rritec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps author and troubleshoot Microsoft Fabric Activator definitions for alerts, notifications, and automated actions so users can build event-driven responses without hand-crafting complex API payloads.

Core Features & Use Cases

Alert and reflex authoring for Fabric sources such as KQL, Digital Twin Builder, Real-time Hub, and Eventstream.
Action automation for Teams messages, email notifications, and Fabric item invocations like pipelines, notebooks, dataflows, and functions.
Definition management with correct entity wiring, rule templates, and update workflows for creating, updating, deleting, and fixing existing Activator items.

Quick Start

Ask for a Microsoft Fabric Activator alert that monitors your chosen source, sets the trigger logic, and generates the full definition payload for deployment.

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 Microsoft Fabric Activator alerts from KQL or Eventstream sources?▼

To create Microsoft Fabric Activator alerts, you need to wire entities from KQL, Eventstream, or Real-time Hub sources and define trigger logic. The process generates a JSON-stringified rule template and Base64-encoded definition parts deployed via Fabric REST calls.

Can I automate Teams notifications and Fabric item invocations using Activator?▼

Yes, you can automate Teams notifications and Fabric item invocations using Activator. The system supports automated actions for Teams messages, email alerts, and triggering pipelines, notebooks, dataflows, and functions based on your defined event-driven rules.

What is the best way to troubleshoot existing Microsoft Fabric Activator definitions?▼

The best way to troubleshoot existing Microsoft Fabric Activator definitions is to validate the entity wiring and ensure the JSON-stringified rule templates are correctly formatted. You can then use update workflows to fix and redeploy the Activator items.

Does the Fabric Activator support Digital Twin Builder and Real-time Hub as source graphs?▼

Yes, the Fabric Activator supports Digital Twin Builder and Real-time Hub as source graphs. It also accommodates KQL and Eventstream sources to build alerts, notifications, and automated actions within your Microsoft Fabric environment.

Why do my Fabric REST calls fail when updating Activator definitions?▼

Fabric REST calls fail when updating Activator definitions if the api.fabric.microsoft.com audience is incorrect or the az rest command lacks properly Base64-encoded definition parts. Ensure your JSON-stringified rule templates and entity wiring are valid before deployment.

Do I need az rest to deploy Microsoft Fabric Activator rules?▼

Yes, you need az rest to deploy Microsoft Fabric Activator rules because the deployment requires making Fabric REST calls to the proper api.fabric.microsoft.com audience. This ensures the Base64-encoded definition parts and rule templates are correctly authored and applied.