Schedule a demo
Schedule A Demo

User Interface

Home Dashboard

The Home section serves as a centralized control panel within the BURQ iPaaS platform. From here, you can gain a quick overview of workspaces, transaction performance, recent activity, and app instances. It is designed for rapid situational awareness and first-step actions.

Key Interface Elements

Workspace Cards

Located at the top of the Home view, each card represents a Workspace. A workspace is a logical container for organizing your dataflows (integration workflows).

  • Example:
    • Shopify BC Flows – Currently shows 0 Enabled Dataflows.
    • Shopify D365 Flows – Displays 6 Enabled Dataflows.
  • Create New Workspace – Clicking the pink-blue “Create” allows users to create a new workspace for additional dataflows.

Transactions Summary Panel

The middle portion of the interface provides a real-time summary of integration transactions.

  • Transaction Status Overview
    • Success Transactions: Transaction completed successfully without errors.
    • Failure Transactions: Transaction failed due to errors and may need attention.
    • Pending Transactions: Transaction queued or in progress, awaiting execution.
  • Transaction Table:
    • Identifier – A unique UUID for each transaction.
    • Dataflow – The dataflow associated with the transaction (e.g., ShopifyD365-OrderInvoice, InventoryUpdate).
    • Created At – The timestamp when the transaction was initiated.

System Health Snapshot

A visual health check appears on the right side of the Home screen:

  • This provides a quick visual indicator of system health.
  • Users can click to view a detailed analytics report of system usage and performance.

Apps and Instances

This section lists currently integrated Apps and their respective Instances:

  • Apps – Total number of app connectors configured (e.g., 8).
  • Instances – Total deployed and online app instances (e.g., 10).
  • Status Indicators – The green dot means the instance is Online.
  • Example-
    • Shopify Store
    • Shopify Store Orchestration

Workspace

The Workspace section is the central hub for managing all your integration dataflows in BURQ. Workspaces are logical groupings of dataflows typically organized around specific applications, systems, or business use cases (e.g., Shopify to D365, WooCommerce to BC).

Each workspace encapsulates a set of dataflows that execute transformation and routing logic between systems.

Key Interface Elements

Workspace Card

Each card represents a unique Workspace, with the following information and actions:

  • Workspace Name – Identifies the integration scope (e.g., ShopifyBCFlows, AmazonD365Flows).
  • Dataflow Count – The number of total dataflows configured within the workspace (e.g., 7 Total Dataflows).
  • + (Add Dataflow) – Quickly initiate the creation of a new dataflow within that workspace.
  • ⋮ (Options Menu) – Opens additional workspace-level actions (e.g., duplicate, export, export to cloud).

Search and View Controls

Located at the top of the Workspace page:

  • Search Bar – Filter workspaces by keyword (e.g., platform name, dataflow type).
  • Toggle Button – Change between different visual layouts for workspace display (e.g., grid or list view).

Create New Workspace

A button labeled “+ Create a new workspace”, located in the top-right, allows users to:

  • Define a new workspace.
  • Name the workspace.
  • Begin configuring initial dataflows.

This supports a modular approach to managing integrations, reducing complexity by grouping related flows.

Dataflows

When you click into a workspace such as ShopifyD365Flows, you are taken to a detailed view where you can monitor and manage all dataflows associated with that specific integration group. On the left side of the screen, you’ll see a searchable list of all your existing workspaces, allowing you to quickly switch between them without needing to return to the main Workspace dashboard.

The main area displays a structured table where each row represents an individual dataflow, showing important operational information:

  • Dataflow Name – A unique identifier for each integration task (e.g., ShopifyD365-ProductCreate).
  • Source and Destination – Indicated with recognizable icons (e.g., Microsoft Dynamics 365 to Shopify), these define where the data originates and where it is sent.
  • Last Run – Displays the timestamp of the most recent execution, useful for tracking activity in near real-time.
  • Transformation – Shows if data mapping or transformation logic is applied before passing the data along.
  • Sync Frequency – Indicates how often the dataflow runs (e.g., every 30 seconds).
  • (Options Menu)-Each row also includes a three-dot options menu that provides access to further actions such as import/export or delete a flow.

This workspace-level view gives you full visibility into the performance, behavior, and setup of each integration. It’s designed to help you manage data movement efficiently and detect issues before they impact connected systems.

Activity Log

This section displays the execution logs for dataflows in the ShopifyD365Flows workspace. Each log provides detailed insight into whether a data flow ran successfully or failed.

Log Entry Example:

  • Type: The log entry shows an Error, indicating that the operation did not complete successfully.
  • Date: The event occurred on July 8, 2025, at 10:30:14 AM.
  • Dataflow: The specific dataflow that encountered the error is ShopifyD365-ProductCreate. This refers to a process intended to create or sync a product from Shopify to Microsoft Dynamics 365.
  • Message:  The system returned the following error:
  • “Status Code: 0. Message: The operation was canceled.”

Technical Note

All workspace and dataflow configurations are persistent and scoped per organization-level access. Each workspace can connect multiple connectors (apps), and support various types of flows such as:

  • Order Sync
  • Inventory Updates
  • Invoice Transfers
  • Shipment Data Exchange

This modular architecture allows teams to manage integrations independently and scale with ease.

Transactions

The Transactions section in BURQ provides a detailed, real-time log of all integration executions across your connected systems. This area acts as your primary monitoring dashboard, allowing you to track whether individual dataflows have run successfully, failed, or are still pending. Each transaction listed represents a single execution instance of dataflow and includes all relevant metadata for operational tracking and troubleshooting.

Key Interface Elements

The table in this view includes the following key elements:

  • ID – A unique identifier assigned to every transaction, useful for audit trails or referencing in support tickets.
  • Workspace – Indicates the name of the workspace where the dataflow resides, helping you contextualize which integration area the transaction belongs to.
  • Dataflow – Specifies the name of the dataflow that was executed, allowing you to see which process the transaction is tied to.
  • Status – Shows the result of the transaction, such as Success or Failure with visual indicators (e.g., green for success).
  • Source ID and Destination ID – These IDs represent the specific records or entities being transferred between applications (e.g., an order ID from Shopify or an invoice ID from Dynamics 365).
  • Detail – This column includes a brief description about process updates, giving you initial insights before diving into debug logs
  • Created At – Displays the timestamp of when the transaction occurred.

Apps

The Apps tab in BURQ displays all the applications you’ve connected to your integration environment. This view serves as a central management panel for your app connectors and their configured instances, essential for establishing communication between different platforms like CRMs, ERPs, eCommerce systems, and more. You can see how many apps are currently in use, how many instances have been deployed, and whether each one is online and ready to process data.

Each card in the Apps view represents an app connector (e.g., Shopify, QuickBooks, Dynamics 365) and shows one or more configured instances beneath it. These instances define the actual authenticated connection between BURQ and a specific account, tenant, or environment of that app. For example, if you’re syncing multiple Shopify stores, each store would be represented as a separate instance under the Shopify connector.

Key Interface Elements

  • App Name – Displayed at the top of each card (e.g., Shopify, WooCommerce, SAP).
  • Instance Count – At the bottom left of each card, you’ll see the total number of instances currently connected as well as the offline instances.

You can see instances of a particular application when clicked.  For instance, if you click Shopify from apps, then you can see:

  • Name- The name of the instance, such as ShopifyStore or ShopifyStoreOrchestration.
  • Status- Indicates the current connection status. A green dot with Online means the instance is active and communicating with the BURQ system.
  • Updated At-Timestamp of the last activity or update for that instance. This helps users monitor freshness and system syncs.
  • Action- Allows the user to click and edit instance settings.

Producers and Consumers – App Instance Configuration

In BURQ, each app instance (like a Shopify or D365 connection) can act as a Producer (data sender) or Consumer (data receiver) within an integration flow. The Producers and Consumers tabs help configure these roles.

Producers Tab

This tab lists services that produce (send) data from the selected application instance.

  • Name- The name of the producer service.
  • FQDN (Fully Qualified Domain Name)-The unique endpoint that identifies the producer in the network. This ensures secure routing and communication across systems.
  • Is Custom Service? – Indicates whether the service was built specifically for this organization (True) or is a standard/preconfigured one (False).
  • Action:
    • Pencil icon: Opens the configuration or editing screen for that producer.
    • Trash icon: Deletes the producer service from the instance.

Consumers Tab

This tab shows services that consume (receive) data in the integration flow.

  • Name- The name of the consumer service. 
  • FQDN (Fully Qualified Domain Name)- The target endpoint where the data will be sent. It typically points to another system or middleware endpoint.
  • Is Custom Service? – Shows if the consumer service is a tailor-made solution (True or a default integration provided by BURQ (False).
  • Action:
    • Pencil icon: Opens the edit settings panel.
    • Trash icon: Removes the consumer from the app instance.

Analytics

The Analytics dashboard provides a real-time and historical overview of your system’s integration performance. It offers insights into transaction volumes, system throughput, error rates, and dataflow-specific performance.

Top KPIs (Top Panel)

  • Total Transactions- This shows the total number of transactions processed in the system (e.g., 7,565). Includes both successful and failed transactions.
  • Peak Throughput- Indicates the highest number of transactions processed in a single burst or peak period (e.g., 315).
  • Apps- Displays the number of applications currently integrated (e.g., 8 apps).
  • Instances- Number of active and configured app instances (e.g., 2 instances).
  • System Health-
    • The pie chart visualizes the Success vs Error ratio.
    • Example: 90.69% of transactions were successful, while 9.31% failed.
    • A health status label (e.g., “Good”) guides users on system performance, with suggestions like “Try to bring your system to excellent health by resolving errors.”

Transaction Timeline (Middle Panel)

  • A time-series graph showing daily transaction volumes.
  • Blue Line–>Successful transactions.
  • Red Line–>Failed transactions.
  • Helps track trends over time and identify dates with error spikes or drops in activity.

System Throughput (Bottom Left Panel)

  • Shows how many transactions are being processed over time.
  • Allows you to identify performance trends across months (e.g., drop in throughput between October and December 2023).
  • Useful for capacity planning and understanding seasonal fluctuations.

Dataflow Transactions (Bottom Right Panel)

  • Bar graph showing transaction counts per dataflow type:
    • AddVariant
    • Order Create
    • Product Update
  • Helps assess which operations are most frequent and which may need optimization or debugging (if errors are high).

This dashboard provides valuable operational intelligence, allowing technical teams to quickly identify bottlenecks, improve performance, and maintain system health.

Settings

The Settings section allows administrators to manage user access, roles, and account statuses. It provides full visibility and control over users interacting with the BURQ integration platform.

Users Tab

This tab lists all registered users on the platform along with their account details and assigned roles. The displayed fields are:

  • Name- Full name of the user for identification within the system.
  • Username- The system-assigned or custom username used during login or internal referencing.
  • Email- The user’s verified email address for communication and login authentication.
  • Status- Indicates the account’s current state:
  • Email Verified- Confirm whether the email has been successfully verified. Required for account activation.
  • Role- Specifies the level of access and permissions:
    • Administrator – Full access to all settings and configurations.
    • Basic – Limited access to specific functionality.
    • ReadOnly – Can only view information; cannot modify or create.
  • Actions:
    • Edit User: Modify user details or role.
    • Lock/Unlock: Temporarily restrict or restore account access.
    • Reset Password: Trigger password reset workflow for the user.
    • Delete User: Permanently remove the user from the system.
  • Create New User- Allows administrators to add a new user by entering basic details (name, email, role). Newly created users typically receive a verification email and login credentials.

This section ensures secure and role-based access control to the integration environment. It supports enterprise-grade user administration for teams working across multiple flows and instances.

Roles Tab

The Roles tab allows administrators to define and manage user roles across the BURQ platform. Each role determines the level of access a user has to various modules and operations.

  • Administrator:
    • Full access to all features.
    • Can add/remove users, manage roles, configure apps, view logs, and adjust system settings.
  • Basic:
    • Access to core functional modules such as Workspaces, Transactions, and Apps.
    • Cannot manage users or system-level configurations.
  • ReadOnly:
    • Can only view data within the platform.Cannot edit configurations, trigger dataflows, or manage users.

About Tab

The About tab in the BURQ platform provides key metadata about the current system deployment. This information is useful for internal auditing, troubleshooting, licensing verification, and environment identification.

  • License GUID- A globally unique identifier (GUID) that represents the current BURQ license. It is used for verifying the legitimacy and scope of platform access.
  • Client Name- Identifies the registered client or organization using this instance of BURQ. This label is often used to separate multiple environments or tenants.
  • Environment- Indicates that this is a live, operational instance. Any configuration or dataflows executed here will affect real systems.

This metadata helps teams confirm that they are operating in the correct environment and that licensing is properly applied.

Debug Logs

The Debug Logs section in BURQ provides a real-time view of background processes, system checks, and service-level activities. This interface helps developers and technical users monitor the operational status and trace potential issues during message processing between integrated systems (e.g., Shopify and D365).

Key Interface Elements

  • Timestamp- The exact time (UTC) when the log entry was generated. This helps track event sequences chronologically.
  • Level- Indicates the severity or purpose of the log. Currently, all entries under this section are categorized as Debug, used for development-level diagnostics.
  • Logger- Identifies the internal process or job that generated the log entry (e.g., StatusCheckJob, PRODUCER_ShopifyD365-OrderCreate).
  • Service- Specifies the associated integration service or module, such as ShopifyD365-OrderCreate or ShopifyD365-ProductUpdate.
  • Transaction ID- Refers to the specific transaction’s unique identifier. If unavailable, it displays as N/A.
  • Message- Contains a summary or status of the logged action. Examples include:
    • “No Bad Data Found.”
    • “0 new messages pulled from source…”
    • “Data service resolved.”
  • Search by Keywords: Allows users to filter logs based on specific text for faster debugging.
  • Auto Refresh Toggle: Enables real-time log updates without manual page refresh.
  • Download & Export Options: Users can export logs for offline review or auditing.

This section is essential for troubleshooting data flow and ensuring proper synchronization across systems, making it a vital tool for developers and support engineers maintaining BURQ integrations.

Packet Logs

The Packet Logs section provides a chronological log of data packets exchanged between integrated systems (e.g., Shopify and Microsoft Dynamics 365) through the BURQ platform. This section is critical for developers and system integrators to monitor API-level communication, especially for troubleshooting failed or incomplete data transactions.

Key Interface Elements

  • Method- Specifies the HTTP method (GET or POST) used in the API request.
  • Software- Indicates the external system involved in the data exchange (e.g., Shopify, D365).
  • Source- Identifies the data origin role. In this context, all logs show the Producer, meaning BURQ initiated the request.
  • Created At- Displays the exact UTC timestamp when the request was generated.
  • Message- Currently marked as N/A; this field is reserved for future use to capture API response messages or error notes.
  • URL- The full API endpoint to which the request was made. This allows developers to trace requests to specific Shopify or D365 routes.
  • Keyword Search- Users can filter logs by entering endpoint fragments or method types (e.g., “orders.json”, “POST”) in the search bar.
  • Advance Filter- allows users to quickly narrow down API records by type, date range, keywords, message ID, or correlation ID for efficient troubleshooting.

This view serves as a transparent record of how and when data packets are transmitted, aiding in pinpointing API failures, timeouts, or misconfigurations in integration.