FlowForger for VS Code

Build Power Automate and Logic Apps flows as TypeScript — with IntelliSense, local debugging, and compilation to Logic Apps JSON.

Features

• IntelliSense: Autocomplete for ctx.* methods, connectors, action names, and variables
• Schema Completions: Inside ctx.connectors.dataverse.* / ctx.connectors.sharepoint.* calls, autocomplete real table logical names, SharePoint sites and lists, and column/field names (in item: {...} keys and $select/$orderby/$filter strings), read live from your environment. Run FlowForger: Connect Data Sources once to sign in — typing never triggers a sign-in prompt on its own.
• Diagnostics: Real-time error detection for invalid references, missing decorators
• Hover Documentation: Rich documentation for methods and decorators
• Snippets: 20+ code snippets for common patterns
• Syntax Highlighting: Special highlighting for FlowForger decorators and methods
• Conditional Breakpoints: Right-click a breakpoint → Edit Condition and enter a DSL-style expression (item.Status === 'Rejected'); the debugger pauses only when it is true. A condition that fails to evaluate or is not a boolean pauses anyway and says why in the Debug Console, so a typo never silently disarms the breakpoint.
• Edit & Continue: While paused, edit the flow and press Restart (Ctrl+Shift+F5) — the run restarts under the hood, replaying recorded connector/HTTP responses (unchanged calls are never re-sent) and fast-forwarding back to the paused position or the first divergence. Restarting while not paused does a normal clean run.
• Set Next Statement: While paused, right-click a line and choose "Jump to Cursor" to move the execution point — backward to re-execute with live connector calls, forward to skip. From a loop-iteration or branch-child pause, a backward jump restarts and replays up to the target instead (console variable edits are not preserved).

File Extension

FlowForger DSL files use the .ff.ts extension.

Connecting to Your Environment

Schema completions, FlowForger: Connect Data Sources, and --auth debug sessions sign in through an app registration in your own Microsoft Entra ID tenant, read from the auth section of flowforger.config.json in your workspace. FlowForger ships no built-in client ID. If you have not set one up yet, the CLI Quickstart walks through it, and flowforger init writes the config file. The extension keeps its own token cache at ~/.flowforger/vscode-token-cache.json and never prompts for sign-in while you type.

Quick Start

1. Create a new file with .ff.ts extension
2. Start typing flow-class to use the snippet
3. Use ctx. to see available methods

Example

Create hello-flow.ff.ts:

@Flow('hello-flow')
class HelloFlow {
  @ManualTrigger()
  trigger() {}

  @Action()
  async run(ctx: FlowContext) {
    // Build a message with a Compose action
    await ctx.compose('Greeting', { message: 'Hello from FlowForger' });

    // POST it to httpbin, which echoes the body back
    await ctx.http('CallHttpBin', {
      method: 'POST',
      url: 'https://httpbin.org/post',
      body: ctx.outputs('Greeting'),
    });

    // Pull the echoed message out of the response
    await ctx.compose('Echo', ctx.body('CallHttpBin')?.['json']);
  }
}

No imports needed. @Flow, @ManualTrigger, @Action, and FlowContext are ambient globals recognized by the FlowForger compiler and this extension. Reference a Compose action's output with ctx.outputs('Name') and an HTTP action's response body with ctx.body('Name').

Commands

• FlowForger: Restart Language Server - Restart the LSP server
• FlowForger: Compile to IR - Compile current file to FlowIR JSON
• FlowForger: Compile to Logic Apps JSON - Compile to Power Automate format

Settings

Requirements

None — the language server, compiler, emitter, and debugger are fully bundled with the extension. No workspace setup or Node.js installation required.

For command-line workflows (CI, deployment), see the flowforger CLI on npm.

License

Apache-2.0