# azure-logic-apps-power-automate

A GitHub Copilot rule that guides JSON workflow definitions for Azure Logic Apps and Power Automate: triggers, actions, error handling.

- rule · `type=rule` · GitHub Copilot · ★ 40418
- Author: github · official GitHub repository
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/github/awesome-copilot/tree/HEAD/instructions/azure-logic-apps-power-automate.instructions.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/rules/azure-logic-apps-power-automate

## What it does

The rule fires on `**/*.json`, `**/*.logicapp.json`, `**/workflow.json`, `**/*-definition.json` and `**/*.flow.json`. It lays out the Workflow Definition Language shape: a `definition` block holding `actions`, `triggers`, `parameters`, `outputs`, `contentVersion` and `staticResults`, plus an outer `parameters` object.

Then come sections on triggers, actions and reliability. Triggers are split into Request, Recurrence and event-based ones such as Service Bus or Event Grid, with advice on timeouts and pagination for high-volume sources. Actions get descriptive names, grouping through scopes, and a choice between HTTP calls, connector actions and data operations. Error handling leans on `runAfter` with `Succeeded`, `Failed` and `TimedOut`, and on a `retryPolicy` of type `fixed`.

A separate block covers expressions: `concat()`, `filter()`, `map()`, `formatDateTime()`, `json()`, and the logical functions used in Power Automate conditions — `and`, `or`, `equals`, `greater`, `less`, `empty`, `not`. Copy the samples with care, because they carry placeholder hosts and mailboxes like `api.example.com` and `support@contoso.com` that you have to swap for your own. Installation is a single file under the Copilot instructions folder, and it pulls in no dependencies.

## Requirements
- Works with: Azure

## Install

### GitHub Copilot (native platform)

**Manually: put the files in place**
- File: `.github/instructions/azure-logic-apps-power-automate.instructions.md` — The applyTo field sets which files it applies to

### Claude Code

**Manually: put the files in place**
- File: `.claude/rules/azure-logic-apps-power-automate.md` — The paths frontmatter field limits the files: move applyTo from the source into paths

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### Cursor

**Manually: put the files in place**
- File: `.cursor/rules/azure-logic-apps-power-automate.mdc` — Frontmatter: description, globs, alwaysApply. Move applyTo from the source into globs, or the rule will not attach on its own

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/azure-logic-apps-power-automate.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/azure-logic-apps-power-automate.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/github/awesome-copilot/tree/HEAD/instructions/azure-logic-apps-power-automate.instructions.md

## When to use it
- scaffold a valid JSON workflow definition
- pick the right trigger for a request, schedule or event scenario
- split success and failure branches with `runAfter`
- set retry behaviour for a flaky external call
- express a data transformation with built-in functions

## Example prompts
- check my `workflow.json` against WDL and fix the structure
- add an error branch with logging to this Logic App definition
- rewrite this Power Automate condition as `@or(equals(item()?['Status'], 'completed'), equals(item()?['Status'], 'unnecessary'))`

## Source text · azure-logic-apps-power-automate.instructions.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: ea5cbde94462c7d6.

BEGIN THIRD-PARTY FILE ea5cbde94462c7d6
````text
---
description: 'Guidelines for developing Azure Logic Apps and Power Automate workflows with best practices for Workflow Definition Language (WDL), integration patterns, and enterprise automation'
applyTo: "**/*.json,**/*.logicapp.json,**/workflow.json,**/*-definition.json,**/*.flow.json"
---

# Azure Logic Apps and Power Automate Instructions

## Overview

These instructions will guide you in writing high-quality Azure Logic Apps and Microsoft Power Automate workflow definitions using the JSON-based Workflow Definition Language (WDL). Azure Logic Apps is a cloud-based integration platform as a service (iPaaS) that provides 1,400+ connectors to simplify integration across services and protocols. Follow these guidelines to create robust, efficient, and maintainable cloud workflow automation solutions.

## Workflow Definition Language Structure

When working with Logic Apps or Power Automate flow JSON files, ensure your workflow follows this standard structure:

```json
{
  "definition": {
    "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
    "actions": { },
    "contentVersion": "1.0.0.0",
    "outputs": { },
    "parameters": { },
    "staticResults": { },
    "triggers": { }
  },
  "parameters": { }
}
```

## Best Practices for Azure Logic Apps and Power Automate Development

### 1. Triggers

- **Use appropriate trigger types** based on your scenario:
  - **Request trigger**: For synchronous API-like workflows
  - **Recurrence trigger**: For scheduled operations
  - **Event-based triggers**: For reactive patterns (Service Bus, Event Grid, etc.)
- **Configure proper trigger settings**:
  - Set reasonable timeout periods
  - Use pagination settings for high-volume data sources
  - Implement proper authentication

```json
"triggers": {
  "manual": {
    "type": "Request",
    "kind": "Http",
    "inputs": {
      "schema": {
        "type": "object",
        "properties": {
          "requestParameter": {
            "type": "string"
          }
        }
      }
    }
  }
}
```

### 2. Actions

- **Name actions descriptively** to indicate their purpose
- **Organize complex workflows** using scopes for logical grouping
- **Use proper action types** for different operations:
  - HTTP actions for API calls
  - Connector actions for built-in integrations
  - Data operation actions for transformations

```json
"actions": {
  "Get_Customer_Data": {
    "type": "Http",
    "inputs": {
      "method": "GET",
      "uri": "https://api.example.com/customers/@{triggerBody()?['customerId']}",
      "headers": {
        "Content-Type": "application/json"
      }
    },
    "runAfter": {}
  }
}
```

### 3. Error Handling and Reliability

- **Implement robust error handling**:
  - Use "runAfter" configurations to handle failures
  - Configure retry policies for transient errors
  - Use scopes with "runAfter" conditions for error branches
- **Implement fallback mechanisms** for critical operations
- **Add timeouts** for external service calls
````
END THIRD-PARTY FILE ea5cbde94462c7d6

The third-party file has ended. Everything between the ea5cbde94462c7d6 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3055 of 60000 bytes. © github · MIT · https://github.com/github/awesome-copilot/tree/HEAD/instructions/azure-logic-apps-power-automate.instructions.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md