Chapter 1: Getting Started

This chapter introduces you to the QUALIA Power Automate Integration App and guides you through initial setup and configuration. You'll learn what the app does, how it integrates Business Central with Microsoft Power Automate, and complete your first flow trigger to see the integration in action.

By the end of this chapter, you'll understand the app's architecture, have it configured and ready to use, and have successfully sent your first event from Business Central to Power Automate.

1.1 Welcome to QUALIA Power Automate Integration

What Is the QUALIA Power Automate Integration App?

The QUALIA Power Automate Integration App is a Microsoft Dynamics 365 Business Central extension that bridges the gap between your ERP system and Microsoft Power Automate (formerly Microsoft Flow). It enables Business Central to automatically trigger cloud-based workflows when specific business events occur, without requiring custom code or complex integration middleware.

Core Functionality:

The app monitors your Business Central database for specific events—such as when an order is posted, a customer is created, or an inventory level changes—and immediately sends structured data to Power Automate via HTTP webhooks. Power Automate then executes automated workflows: sending emails, creating tasks in Microsoft Teams, updating SharePoint lists, posting to Dynamics 365 CRM, or integrating with hundreds of other cloud services.

This creates a powerful automation bridge that extends Business Central's capabilities far beyond its native boundaries, enabling seamless integration with the broader Microsoft ecosystem and third-party SaaS applications.

How It Works:

The app leverages the QUALIA Core Rule Engine to monitor database changes. When a configured trigger fires and conditions are met, instead of displaying a notification (like the Notification App), it makes an HTTP POST request to a Power Automate webhook URL, sending JSON-formatted data about the business event. Power Automate receives this webhook, extracts the data, and executes whatever workflow you've designed—all in real-time, automatically, without user intervention.

Key Benefits and Business Value

1. Extend Business Central Without Programming

Traditional Business Central integrations require AL development, Visual Studio Code setup, extension deployment, and ongoing maintenance. The Power Automate Integration App eliminates this complexity:

• Configure integrations through Business Central's standard interface

• No AL code required for basic integrations

• No extension deployment for simple workflows

• Changes take effect immediately without compilation or publishing

Business analysts and power users can create integrations that previously required developer resources.

2. Real-Time Business Process Automation

Events in Business Central trigger immediate action in connected systems:

• Order posted → Email sent to warehouse within seconds

• Credit limit exceeded → Alert created in Microsoft Teams immediately

• New customer created → Record added to CRM system instantly

• Inventory below threshold → Procurement notification sent to buyer

This real-time connectivity enables responsive business processes that react to events as they happen, not hours later when batch jobs run.

3. Leverage the Power Automate Ecosystem

Power Automate provides 400+ connectors to cloud services:

• Communication: Outlook, Gmail, Teams, Slack, Twilio SMS

• Productivity: SharePoint, OneDrive, OneNote, Planner

• CRM: Dynamics 365 Sales, Salesforce, HubSpot

• Social: Twitter, LinkedIn, Facebook

• Analytics: Power BI, Excel Online, SQL Server

• Workflow: Approvals, Forms, Notifications

• Custom: HTTP requests, Azure Functions, custom APIs

One Business Central event can trigger actions across multiple systems simultaneously.

4. Reduce Manual Data Entry and Errors

Automated data flow eliminates manual information transfer:

• Sales order data automatically creates SharePoint list items

• Customer information syncs to marketing automation platforms

• Financial data exports to analytics tools

• Inventory movements update warehouse management systems

Reducing manual data entry reduces transcription errors and frees staff for higher-value work.

5. Enable Citizen Developer Integration

Power Automate's visual, low-code interface democratizes integration:

• Business users can build and modify flows

• IT maintains governance and security

• Rapid prototyping and iteration

• Lower total cost of ownership compared to custom development

Organizations can respond faster to changing integration needs without backlog delays.

6. Audit Trail and Monitoring

Every HTTP request is logged in Business Central's validation log:

• When the trigger fired

• What data was sent

• HTTP response code received

• Success or failure status

• Error messages for troubleshooting

Plus, Power Automate provides its own run history, giving end-to-end visibility into integration execution.

💡 TIP: Start with simple, high-value integrations to demonstrate ROI quickly. Common quick wins include order confirmation emails, customer welcome workflows, and inventory alerts. Build confidence and skills before tackling complex multi-system integrations.

Who Should Use This Manual?

This manual is designed for multiple audiences involved in Business Central and Power Automate integration:

Business Central Administrators:

• Responsible for configuring flow triggers in Business Central

• Managing templates and integration configurations

• Monitoring integration health and troubleshooting issues

• Understanding security and permission requirements

Power Automate Flow Designers:

• Building flows that receive Business Central webhooks

• Parsing JSON payloads from Business Central

• Designing multi-step automated workflows

• Testing and debugging flow execution

Business Analysts:

• Identifying automation opportunities

• Documenting business requirements for integrations

• Working with both BC admins and flow designers to implement solutions

• Validating that integrations meet business needs

IT Managers and Solution Architects:

• Understanding architecture and integration patterns

• Planning enterprise-scale integration strategies

• Evaluating security and compliance implications

• Overseeing governance and best practices

Prerequisites for Using This Manual:

You should have:

• Business Central access: Ability to configure and manage integration settings

• Power Automate access: Microsoft 365 or Dynamics 365 license with Power Automate included

• Basic Business Central knowledge: Familiarity with tables, fields, and records

• Basic Power Automate knowledge: Understanding of flows, triggers, and actions (or willingness to learn)

• JSON familiarity: Helpful but not required—examples provided throughout

This manual assumes no AL programming knowledge. Advanced customization requiring codeunit development is beyond scope but referenced where relevant.

How to Use This Manual

Learning Path:

This manual follows a progressive learning structure:

Chapters 1-2 (Foundation): Understand what the app does, how it works, and complete basic setup. Start here if you're new to the integration.

Chapters 3-4 (Configuration): Learn to create and configure flow triggers, work with placeholders, and set up conditions. This is core operational knowledge for BC administrators.

Chapter 5 (Power Automate): Build flows that receive BC webhooks and process data. Essential for flow designers.

Chapter 6 (Operations): Troubleshoot issues, optimize performance, and follow best practices. Reference material for ongoing operations.

Appendices (Reference): Quick-lookup resources for placeholders, JSON structures, error codes, and troubleshooting.

Reading Strategies:

First-Time Users: Read Chapters 1-2 completely, then work through the Quick Start Tutorial (section 1.5). This gives you foundational understanding and hands-on experience.

BC Administrators: Focus on Chapters 1, 3, and 4. Skim Chapter 5 to understand what flow designers need from you.

Flow Designers: Read sections 1.1-1.2 for context, then focus heavily on Chapters 2 and 5. Reference Chapter 3 to understand payload structure.

Troubleshooters: Jump directly to Chapter 6 and the appendices. Use the troubleshooting checklist (Appendix D) as a diagnostic tool.

Visual Indicators Throughout This Manual:

This manual uses consistent visual indicators to highlight important information:

📋 NOTE: Supplementary information, background context, or clarifications that provide additional depth without being critical to the main content.

⚠️ WARNING: Critical information about potential problems, data loss risks, security concerns, or common mistakes that can cause significant issues if ignored.

💡 TIP: Practical advice, shortcuts, best practices, or expert recommendations that make your work easier or more efficient.

✅ EXAMPLE: Real-world scenarios, sample configurations, or concrete illustrations demonstrating concepts in action.

Pay special attention to warnings—they help you avoid common pitfalls and problematic configurations.

1.2 System Overview

How the App Works with Business Central

The QUALIA Power Automate Integration App is installed as a Business Central extension (per-tenant extension or AppSource app). It extends Business Central's functionality without modifying core application code, ensuring compatibility with Business Central updates and other extensions.

System Architecture:

Component Overview:

1. QUALIA Core Rule Engine (Base Dependency):

• Monitors Business Central tables for database events

• Evaluates triggers (which tables, which events)

• Validates scenarios (conditional logic)

• Provides rule groups for user targeting

• Shared foundation with other QUALIA apps

2. Power Automate Detail Extension (Table 72777824):

• Stores webhook URL for each flow trigger

• Contains JSON payload template with placeholders

• Links to trigger and scenario configuration

• Inherits from QUALIA Core's Validation Detail table

3. Integration Pages (72778130-72778133):

• User interface for configuring flow triggers

• List page showing all configured integrations

• Card page for detailed configuration

• Setup page for global settings

• Template import/export functionality

4. HTTP Client Logic:

• Constructs HTTP POST requests

• Resolves placeholders in JSON payload

• Adds standard headers (Content-Type: application/json)

• Sends to configured webhook URL

• Logs response in validation log

5. Validation Log (Table 72777800):

• Records every trigger evaluation

• Captures HTTP request/response

• Stores error messages

• Provides troubleshooting information

Integration with QUALIA Core Rule Engine

The Power Automate Integration App doesn't reinvent the wheel—it leverages the robust trigger and scenario engine from QUALIA Core:

Shared Functionality:

Triggers: Configure which tables to monitor, which events to catch (Insert/Modify/Delete/Rename), and which fields matter (trigger strings). This is identical to the Notification App's trigger configuration.

Scenarios: Create conditional formulas using placeholders, comparison operators, and logical expressions. Flow triggers only fire when scenario conditions evaluate to true.

Rule Groups: Optionally filter which users trigger integrations. If a user not in the assigned rule group modifies a record, the integration won't fire.

Validation Sets: The overarching configuration object that ties triggers, scenarios, and action details together.

Unique to Power Automate Integration:

Instead of displaying a notification or sending an email, the Rule Engine calls the Power Automate-specific action handler, which:

1. Retrieves the webhook URL from Power Automate Detail

2. Constructs JSON payload by resolving placeholders

3. Makes HTTP POST request

4. Logs the result

This architecture means you already know 80% of configuration if you've used any other QUALIA app—only the action details (webhook URL and JSON payload) are unique.

📋 NOTE: The QUALIA Core Rule Engine must be installed and configured before the Power Automate Integration App will function. Version 1.1.0.4 or higher is required. The app won't install without this dependency.

Understanding the Webhook Workflow

Webhooks are HTTP callbacks—a way for one system to notify another system in real-time when events occur:

Webhook Flow in Detail:

Step 1: Configure Flow Trigger in Business Central

• Administrator creates flow trigger configuration

• Specifies webhook URL from Power Automate

• Designs JSON payload template with placeholders

• Configures triggers (table, events, fields)

• Sets up scenarios (conditional logic)

Step 2: Business Event Occurs

• User posts a sales order, creates a customer, updates inventory, etc.

• Business Central executes database operation (INSERT, UPDATE, DELETE)

• Transaction commits to database

Step 3: Rule Engine Detects Event

• QUALIA Core subscribers on table events fire

• Rule Engine identifies matching triggers

• Flow trigger is marked for evaluation

Step 4: Trigger and Scenario Evaluation

• System checks if trigger conditions met (correct table, event type, field changes)

• Evaluates scenario formulas against record data

• Checks rule group membership if configured

• Determines whether to proceed

Step 5: Payload Construction

• System retrieves JSON payload template

• Resolves all placeholders to actual field values

• Formats dates, numbers, and booleans correctly

• Creates complete JSON document

Step 6: HTTP POST Request

• System makes HTTPS request to webhook URL

• Sets Content-Type: application/json header

• Includes JSON payload in request body

• Waits for response (with timeout)

Step 7: Power Automate Receives Webhook

• Flow's HTTP trigger fires

• Power Automate parses JSON body

• Extracts data fields for use in flow actions

Step 8: Flow Execution

• Power Automate executes workflow steps

• May send emails, create records, call APIs, etc.

• Handles errors and retries as configured

Step 9: Response and Logging

• Power Automate returns HTTP response (200 OK, 400 Bad Request, etc.)

• Business Central logs response in validation log

• Success/failure recorded for monitoring

Step 10: Business Central Continues

• Original Business Central operation completes normally

• User sees no delay or interruption

• Integration happens asynchronously in background

Timing Considerations:

• Entire webhook process typically completes in 1-3 seconds

• Business Central doesn't wait for flow execution—only for HTTP acknowledgment

• Long-running flows don't block BC operations

• Failures don't prevent BC operation from completing

⚠️ WARNING: If Power Automate is unreachable (network issue, webhook URL invalid, service outage), the HTTP request will fail and be logged as an error. The Business Central operation still completes successfully—the integration failure doesn't roll back the database transaction. Monitor validation logs to catch integration failures.

Understanding JSON Payloads

JSON (JavaScript Object Notation) is a lightweight data format for transmitting structured information between systems. The Power Automate Integration App sends data from Business Central to Power Automate as JSON.

Basic JSON Structure:

{
  "OrderNo": "SO-001",
  "CustomerName": "Alpine Ski House",
  "OrderDate": "2025-12-01",
  "Amount": 15450.00,
  "Status": "Released"
}

This JSON object contains five name-value pairs (properties). Each property has a name (key) and a value.

Why JSON?

• Universal: Every modern system can read/write JSON

• Human-readable: Easy to understand and debug

• Structured: Represents complex data hierarchies

• Lightweight: Minimal formatting overhead

• Power Automate native: Flows easily parse JSON

JSON in Flow Triggers:

You design a JSON template in the flow trigger configuration:

{
  "OrderNo": "[36:3]",
  "CustomerName": "[36:79]",
  "Amount": [36:110]
}

The placeholders ([36:3], [36:79], [36:110]) resolve to actual values when the trigger fires:

{
  "OrderNo": "SO-001",
  "CustomerName": "Alpine Ski House",
  "Amount": 15450.00
}

Power Automate receives this complete JSON and can reference individual properties in flow actions.

💡 TIP: You don't need to be a JSON expert to use this app. The manual provides templates and examples for common scenarios. Copy, paste, and modify property names and placeholders to suit your needs. Power Automate's "Parse JSON" action handles the extraction automatically.

Power Automate Basics

If you're new to Microsoft Power Automate, here's a brief introduction:

What Is Power Automate?

Power Automate is Microsoft's cloud-based workflow automation platform (formerly Microsoft Flow). It allows you to create automated workflows ("flows") that connect apps and services, moving data between them and performing actions based on triggers.

Key Concepts:

Trigger: The event that starts a flow

• Examples: "When an HTTP request is received", "When an email arrives", "When a file is created"

• Our integration uses the "When an HTTP request is received" trigger

Actions: The steps a flow performs

• Examples: "Send an email", "Create a SharePoint item", "Post to Teams"

• Flows can have multiple actions in sequence or parallel

Connectors: Pre-built integrations to services

• Over 400 connectors available

• Each connector provides triggers and actions

• Examples: Outlook, SharePoint, SQL Server, Twitter

Flow Types:

• Automated flows: Triggered by events (our use case)

• Instant flows: Triggered manually by button click

• Scheduled flows: Run on a schedule (daily, hourly, etc.)

Accessing Power Automate:

1. Navigate to https://make.powerautomate.com

2. Sign in with your Microsoft 365 or Dynamics 365 credentials

3. Click "Create" → "Automated cloud flow"

4. Build your flow using the visual designer

Licensing:

Power Automate is included with:

• Microsoft 365 subscriptions (Office 365 E3, E5, Business Premium)

• Dynamics 365 licenses

• Standalone Power Automate plans

Premium connectors and high-volume scenarios may require additional licensing. Check with your IT department or Microsoft licensing specialist.

📋 NOTE: This manual assumes you have Power Automate access and basic familiarity with creating flows. If you're completely new to Power Automate, consider completing Microsoft's introductory training at https://docs.microsoft.com/learn/powerautomate/ before proceeding with complex integrations.

1.3 Prerequisites and Setup

System Requirements

Before installing and configuring the Power Automate Integration App, verify your environment meets these requirements:

Business Central Platform Requirements:

• Microsoft Dynamics 365 Business Central version 15.0 or later

• Business Central on-premises or SaaS (cloud) supported

• Web client required for configuration (desktop client not supported for extension pages)

• Modern browser: Chrome, Edge, Firefox, or Safari

QUALIA Core Dependency:

• QUALIA Core Rule Engine version 1.1.0.4 or higher must be installed

• Without QUALIA Core, the Power Automate app cannot function

• QUALIA Core provides the trigger and scenario engine

Power Automate Requirements:

• Microsoft 365 subscription with Power Automate included OR Dynamics 365 license with Power Automate rights OR standalone Power Automate license

• Ability to create and publish flows

• Sufficient API call quota for expected integration volume

Network Requirements:

• Business Central must have outbound HTTPS access to Power Automate endpoints

• Firewall rules allowing HTTPS (port 443) to *.logic.azure.com domains

• No SSL inspection or man-in-the-middle proxies breaking HTTPS certificates

📋 NOTE: Business Central SaaS customers automatically have outbound internet access. On-premises customers must verify network configuration allows HTTPS to external services.

License Requirements

Business Central Licensing:

The Power Automate Integration App requires:

• Business Central user license (Essentials, Premium, or Team Member depending on usage)

• Permissions to configure validation sets and triggers (typically administrators or super users)

QUALIA Licensing:

Two licensing models exist:

1. Full License Model:

• Requires QUALIA Core license plus Power Automate Integration App license

• Purchased separately or as part of QUALIA suite

• Contact your Business Central partner or QUALIA vendor

2. Unlicensed Model:

• Limited functionality or trial mode

• May restrict number of flow triggers or execution volume

• Upgrade to full license for production use

Check with your Business Central partner for licensing specifics in your environment.

Power Automate Licensing:

Power Automate usage is subject to Microsoft's fair use policies:

• Standard connectors: Generous limits included in Microsoft 365

• Premium connectors: May require Power Automate per-user or per-flow license

• High volume: May trigger throttling or require Power Automate per-flow plan

Monitor your flow runs at https://make.powerautomate.com to track usage against your plan limits.

Initial Configuration Steps

Once prerequisites are met, configure the app:

Step 1: Verify QUALIA Core Installation

1. Open Business Central

2. Search for "QUA Validation Sets" using Alt+Q

3. If the page opens, QUALIA Core is installed

4. If "page not found" error appears, install QUALIA Core first

To check QUALIA Core version:

1. Search for "Extension Management"

2. Find "QUALIA Core Rule Engine" in the list

3. Verify version is 1.1.0.4 or higher

4. If older version, update QUALIA Core before proceeding

Step 2: Verify Power Automate App Installation

1. Search for "Extension Management"

2. Find "QUALIA Power Automate Integration" in the list

3. Verify status is "Installed" and "Enabled"

4. If not present, install from AppSource or deploy per-tenant extension

Step 3: Configure Number Series

Flow triggers can use number series for automatic code assignment:

1. Search for "QUA Power Automate Setup"

2. Open the setup page

3. In the Validation Set Numbering field, click the dropdown

4. Select an existing number series or create a new one

To create a new number series:

1. Click New or Advanced from the number series dropdown

2. Set Code: PA-FLOW

3. Set Description: Power Automate Flow Triggers

4. In the Lines section, add a line:

   • Starting No.: PA-00001

   • Ending No.: PA-99999

   • Increment-by No.: 1

5. Check Default Nos. to enable auto-assignment

6. Save and close

Step 4: Enable the Integration

1. In QUA Power Automate Setup, ensure Enable Business Rule is checked

2. If unchecked, no flow triggers will fire (master off-switch)

3. Save the setup page

Step 5: Assign User Permissions

Users need appropriate permissions:

Option A: Assign Permission Set to Individual Users

1. Search for "Users"

2. Select a user

3. Click User Permission Sets

4. Add QUA Power Automate - View (read-only configuration access) OR QUA Power Automate - Edit (full configuration access)

Option B: Assign to User Groups

1. Search for "User Groups"

2. Select a group (e.g., "ADMINISTRATORS")

3. Click User Group Permission Sets

4. Add the appropriate QUALIA permission set

Permission Set Descriptions:

• QUA Power Automate - View: Can view flow trigger configurations but not modify

• QUA Power Automate - Edit: Can create, modify, and delete flow triggers

• SUPER: Full access to all functionality (administrators)

📋 NOTE: Users don't need permissions to "trigger" integrations—only to configure them. When a user posts an order (for example), the integration fires automatically regardless of that user's permissions, as long as the integration is configured by someone with edit rights.

Step 6: Verify Installation

Confirm everything is working:

1. Search for "QUA Power Automate Triggers"

2. The list page should open (may be empty initially)

3. Click New to test creating a new flow trigger

4. If the card page opens, installation is successful

5. Close without saving (or create a test trigger if ready)

⚠️ WARNING: Don't import default templates until you understand webhook URLs and have Power Automate flows ready to receive webhooks. Default templates contain placeholder URLs that won't work without corresponding flows.

1.4 User Interface Overview

QUA Power Automate Triggers List Page

The main interface for managing flow triggers is the QUA Power Automate Triggers list page.

Accessing the List Page:

• Press Alt+Q to search

• Type "QUA Power Automate Triggers" or "Power Automate"

• Select from results

Page Layout:

The list displays all configured flow triggers in a grid:

Columns:

• Code: Unique identifier (e.g., "PA-00001", "ORDER-POSTED")

• Description: Human-readable explanation of what this integration does

Ribbon Actions:

New: Creates a new flow trigger and opens the card page for configuration.

Edit: Opens the selected flow trigger's card page for modification.

Delete: Removes the selected flow trigger and all associated configuration (triggers, scenarios). This action cannot be undone.

Create Default Data: Imports pre-configured example flow triggers from embedded XML resource. Use with caution—overwrites existing triggers with matching codes.

Import: Loads flow trigger configurations from XML file. Use for migrating configurations between environments or restoring backups.

Export: Saves selected flow triggers (or all if none selected) to XML file for backup or migration.

💡 TIP: Use consistent naming conventions for codes. Prefixes like "PA-" help identify Power Automate triggers vs. other QUALIA validation sets. Descriptive names like "ORDER-POSTED" or "CUST-CREATED" are more maintainable than generic numbers.

Flow Trigger Card Page

The card page is where you configure all aspects of a flow trigger:

General Section:

Code: Unique identifier, auto-assigned from number series or manually entered Description: Explanation of the integration's purpose

Power Automate Details Section:

Webhook URL: The full HTTPS URL of the Power Automate flow's HTTP trigger JSON Payload: The template defining what data to send (with placeholders)

Triggers & Scenarios Section:

This section is an embedded page from QUALIA Core:

Triggers Subpage: Defines which table, which events (Insert/Modify/Delete), and which fields trigger evaluation Scenarios Subpage: Defines conditional formulas that must evaluate to true Rule Group Subpage: Optionally filters which users trigger this integration

Lookup Placeholder FactBox:

The right side of the page includes a FactBox for finding placeholder values:

• Select a table to see its fields

• Click fields to see placeholder format

• Copy placeholders to use in JSON payload

QUA Power Automate Setup Page

Global settings for the integration:

Accessing Setup:

• Search for "QUA Power Automate Setup"

Fields:

Enable Business Rule: Master on/off switch. When unchecked, NO flow triggers will fire, regardless of individual configurations.

Validation Set Numbering: Number series for auto-assigning codes to new flow triggers.

📋 NOTE: The setup page affects ALL flow triggers. Use "Enable Business Rule" checkbox to temporarily disable all integrations for maintenance or troubleshooting without deleting individual configurations.

Navigation Patterns

From List to Card:

• Click any row to open that flow trigger's card

• Or select row and click Edit

• Or press Enter when row is selected

Within Card Page:

• Tab between fields

• Click into embedded subpages to add/edit rows

• Use FactBox to look up placeholders

• Ctrl+S to save

Creating New Flow Triggers:

• From list page, click New

• System opens blank card

• Code is pre-populated from number series

• Configure all sections

• Save when complete

1.5 Quick Start Tutorial

Creating Your First Flow Trigger

This tutorial walks you through creating a complete integration that sends sales order data from Business Central to Power Automate when an order is posted.

Scenario: When a sales order is posted, send order number, customer name, and total amount to a Power Automate webhook, which then sends an email notification.

Part A: Create the Power Automate Flow

First, create the flow that will receive data from Business Central:

Step 1: Create a New Flow

1. Navigate to https://make.powerautomate.com

2. Click Create in the left menu

3. Select Automated cloud flow

4. Click Skip (we'll configure the trigger manually)

Step 2: Add HTTP Trigger

1. Search for "HTTP" in the connector search

2. Select When an HTTP request is received trigger

3. The trigger is added to your flow

Step 3: Generate the Webhook URL

1. Leave the Request Body JSON Schema blank for now

2. Click Save (top right)

3. After saving, the trigger expands and shows a HTTP POST URL

4. Click the Copy icon to copy this URL

5. Paste the URL into Notepad—you'll need it in Business Central

Example webhook URL:

📋 NOTE: This URL is unique to your flow and includes authentication tokens. Treat it as sensitive—anyone with this URL can trigger your flow.

Step 4: Add Email Action

1. Click + New step below the HTTP trigger

2. Search for "Send an email" (Outlook or Office 365 Outlook)

3. Select Send an email (V2)

4. If prompted, sign in to Outlook and authorize the connection

5. Configure the email:

   • To: Your email address (for testing)

   • Subject: New Order Posted: {orderNo}

   • Body: Order {orderNo} posted for customer {customerName}. Total: ${amount}

Step 5: Add Dynamic Content

1. Click in the Subject field where you typed {orderNo}

2. Delete {orderNo} and click Add dynamic content

3. Select See more next to the HTTP trigger

4. You'll see limited options now—this is fine

5. For now, use literal text: "New Order Posted"

6. We'll improve this after the first successful webhook

Step 6: Save the Flow

1. Name your flow: "BC Sales Order Posted Notification"

2. Click Save

3. Leave the flow editor open—we'll return after testing

Part B: Configure the Flow Trigger in Business Central

Now configure Business Central to send data to this flow:

Step 1: Create Flow Trigger

1. In Business Central, search for "QUA Power Automate Triggers"

2. Click New

3. Code is auto-assigned (e.g., "PA-00001")

4. Enter Description: Sales Order Posted Integration

Step 2: Configure Webhook URL

1. In the Power Automate Details section, find Webhook URL field

2. Paste the URL you copied from Power Automate

3. Verify it starts with https:// and contains .logic.azure.com

Step 3: Design JSON Payload

1. In the JSON Payload field, enter:

{
  "orderNo": "[36:3]",
  "customerName": "[36:79]",
  "amount": [36:110],
  "orderDate": "[36:13]"
}

This defines four data fields to send:

• orderNo: Sales Header No. field (placeholder [36:3])

• customerName: Sell-to Customer Name (placeholder [36:79])

• amount: Amount Including VAT (placeholder [36:110])

• orderDate: Order Date (placeholder [36:13])

Step 4: Configure Trigger

1. Scroll to the Triggers & Scenarios section

2. In the Triggers subpage, add a new line:

   • Source Table No.: 36 (Sales Header)

   • Trigger Insert: Check this box

   • Trigger Modify: Uncheck

   • Trigger Delete: Uncheck

   • Trigger String: Leave blank

Why these settings?

• Table 36 is Sales Header (orders)

• Trigger Insert fires when new records are created

• Posted orders are inserted into Posted Sales Invoice Header table

• Actually, wait—posted orders INSERT into table 112 (Sales Invoice Header), not modify table 36

Let's correct this:

• Source Table No.: 112 (Sales Invoice Header—for posted orders)

• Trigger Insert: Check this box

• This way we catch posted sales invoices

Step 5: Add Scenario (Optional) For this simple tutorial, we'll skip scenarios. The integration will fire for EVERY posted sales invoice.

In production, you might add scenarios like:

• Only orders above $10,000: [112:110] > 10000

• Only specific customers

• Only certain salesperson codes

Step 6: Assign Rule Group (Optional) Skip rule groups for now—let all users trigger this integration.

Step 7: Save

1. Press Ctrl+S or click OK

2. The flow trigger is now active

Part C: Test the Integration

Step 1: Post a Sales Invoice

1. Search for "Sales Invoices" in Business Central

2. Create a new sales invoice or open an existing unposted one

3. Fill in:

   • Customer: Any customer (e.g., "10000 Adatum Corporation")

   • Add at least one line item

   • Verify total amount calculates

4. Click Post → Ship and Invoice

5. Confirm posting

Step 2: Verify Webhook Sent

1. Search for "QUA Validation Log"

2. Filter to recent entries (today's date)

3. Find an entry with Validation Set ID = "PA-00001" (your flow trigger code)

4. Check the Status column:

   • Success: HTTP request succeeded (200 OK response)

   • Error: HTTP request failed (see error message)

Step 3: Check Power Automate

1. Return to https://make.powerautomate.com

2. Click My flows in left menu

3. Find your flow "BC Sales Order Posted Notification"

4. Click on the flow name

5. You should see a run in the 28-day run history

6. Click on the run to see details

Step 4: Verify Email

1. Check your email inbox

2. You should receive an email with subject "New Order Posted"

3. Body contains placeholder data (we'll improve this next)

If It Worked: Congratulations! You've successfully integrated Business Central with Power Automate. Data flowed from BC to the cloud and triggered an automated action.

If It Didn't Work: See Troubleshooting section (Chapter 6) or check these common issues:

• No validation log entry: Trigger didn't fire. Check table number and trigger type.

• Validation log shows error: Check webhook URL is correct and complete.

• Flow didn't run: Webhook URL might be wrong. Regenerate in Power Automate.

• Email didn't arrive: Check Outlook connection in Power Automate flow.

Part D: Improve the Flow with Dynamic Data

Now let's make the email use actual data from Business Central:

Step 1: Generate JSON Schema in Power Automate

1. In Power Automate, open your flow for editing

2. Click on the HTTP trigger to expand it

3. Find Request Body JSON Schema

4. Click Use sample payload to generate schema

5. Paste this sample (matching your payload structure):

{
  "orderNo": "SI-001",
  "customerName": "Adatum Corporation",
  "amount": 15450.50,
  "orderDate": "2025-12-01"
}

6. Click Done

7. Power Automate generates the schema automatically

Step 2: Update Email with Dynamic Content

1. Click on the Send an email action

2. Clear the Subject field

3. Type: "New Order Posted: "

4. Click in the dynamic content panel

5. Select orderNo (now available thanks to the schema)

6. Clear the Body field

7. Type:

Order: [select orderNo from dynamic content]
Customer: [select customerName]
Amount: $[select amount]
Date: [select orderDate]

Step 3: Save and Test Again

1. Save the flow

2. Post another sales invoice in Business Central

3. Check your email

4. This time, it should show actual order data!

✅ EXAMPLE - Expected Email:

Understanding What Happened

Let's review the complete flow:

1. You posted a sales invoice in Business Central

2. BC inserted a record into table 112 (Sales Invoice Header)

3. QUALIA Rule Engine detected the insert event

4. Flow trigger evaluated: Table 112, Insert event matched

5. No scenarios so condition automatically passed

6. JSON payload constructed: Placeholders resolved to actual values

7. HTTP POST sent to your webhook URL

8. Power Automate received the webhook

9. HTTP trigger fired and provided data to flow

10. Email action executed using dynamic content

11. You received email with order details

All of this happened in 2-3 seconds, automatically, without any user intervention after the initial post action.

Next Steps

Now that you have a working integration, consider:

Enhance the email:

• Add conditional formatting (HTML body)

• Include more data fields (customer email, phone, address)

• Format currency with proper symbols

• Add links back to Business Central

Add error handling:

• Use Power Automate's parallel branches and error scopes

• Send failure notifications

• Retry failed HTTP calls

Create additional integrations:

• Customer created → Add to CRM

• Inventory low → Create Teams alert

• Payment received → Update SharePoint list

• Approval needed → Start approval workflow

Add conditional logic:

• Use scenarios in BC to filter which orders trigger

• Use conditions in Power Automate to branch logic

• Combine both for precise control

💡 TIP: Start with this simple pattern and incrementally add complexity. Don't try to build the perfect integration on day one. Get something working, learn from it, then enhance.

This completes Chapter 1. You now understand the system, have it configured, and have successfully created and tested your first Business Central to Power Automate integration.