Integrations

Every instrument and system, one connected record

A Digital Scientist can only judge what it can see. Quickflow takes data from the instruments, equipment and enterprise systems you already run, at the source and with its audit trail, and hands results on without a second copy.

See it with your systems What connects

Protocols and platforms

Empower
Chromeleon
OpenLab
OPC UA
Modbus TCP
BACnet/IP
OPC HDA
RS-232/485
MQTT
AMQP
REST
GraphQL
SOAP
Webhooks
FTP/FTPS
AWS S3
Azure Data Lake
SAP
LIMS
Active Directory

Quickflow

One record

Empower · Chromeleon. Processed results pulled from the CDS, never retyped

CDS

Processed chromatography results, taken from the CDS with their version. Nobody retypes a peak area.

Empower
Chromeleon
OpenLab

Non-CDS instruments

Balances, meters and spectrometers, over serial, network or the files they write.

RS-232/485
Ethernet
File capture

OPC UA and plant protocols

Live signals from PLCs, SCADA, building systems and historians, over the interfaces they already have.

OPC UA
Modbus TCP
BACnet/IP
OPC HDA

Enterprise systems

Links to the systems that plan, record and release, so master data is entered once.

LIMS
SAP / ERP
eBMR / MES
HRMS

APIs and web services

REST, GraphQL and SOAP, so modern apps and older pharma systems both connect, plus webhooks for events.

REST
GraphQL
SOAP
Webhooks

Messaging, files and cloud

Message brokers that send and receive, secure file transfer, and delivery into your data lake on AWS or Azure.

MQTT
AMQP
FTP/FTPS
AWS data lake
Azure data lake

Integration architecture

From the bench and the plant floor to the enterprise

Five layers, one path. Each value climbs from the instrument that measured it, through the connector that suits it, into the validated platform, and on to the applications and systems that act on it.

Enterprise systems

Plan, record, release

LIMS
SAP / ERP
eBMR / MES
HRMS
Training (LMS)
CMMS
RIMS
SIEM
Data lake (AWS, Azure)
Your own tools

Quickflow applications

Where the work is done

Quickflow platform

Validated, on AWS

AWS · Mumbai by default

Audit trail from capture
Part 11 e-signatures
Active Directory SSO
AI on Amazon Bedrock
Dev → QA → Prod on approval

Connectors

The right one for each source

CDS connector. Results are taken from the processed result in the CDS, with the result version recorded.

Lab and plant floor

Instruments, equipment and software you already run

HPLC, GC, LC-MS
UV-Vis, FTIR
Balances
pH meters
Freezers, chambers
PLC, SCADA
BMS, HVAC
Plant historian
Legacy software

Data in, captured at source Results and events out

Integration catalogue

Everything Quickflow connects to

CDS and the instruments behind it, standalone lab instruments, plant equipment, enterprise systems, identity and security, web services, messaging, files and cloud storage. Pick a group to narrow the list.

Something you run is not listed? Tell us what it is and we will show how it connects.

CDS and non-CDS instruments

The number is captured, not copied

Each value reaches the record straight from where it was measured: the CDS, the balance, the meter, the file the instrument writes, or its screen. The source, time and person travel with it.

Worksheet AT-114 · Assay by HPLC

Connected

Source: Empower · QC-HPLC-07
Interface: CDS connector
Peak area, main peak: 1 482 913
Captured: 09:41:07 IST · equipment clock
Analyst: P. Shah (psha)

Audit trail entry written

Taken from the processed result, with its result version recorded.

Illustrative values and IDs.

Plant and facility

Speaks the protocols your equipment already uses

No new sensors and no rewiring. Quickflow listens on the interfaces already on site, and readings arrive within seconds carrying the time the equipment recorded.

BMS and HVAC

Room pressure, humidity, air handler status

BACnet/IP

RM-114 ΔP

15.2 Pa

Environmental monitoring

Particle counters and cleanroom sensors

OPC UA

ISO-01 ≥0.5 µm

537 /m³

PLC and SCADA

Autoclaves, isolators, WFI loops, reactors

OPC UA · Modbus TCP

WFI-L1 temp

81.6 °C

Standalone equipment

Freezers, stability chambers, data loggers

RS-232/485 · Quickflow Edge

SC-03 RH

75.7 %

Plant historian

Tags and alarm history already on site

OPC HDA · REST

Historian

1,249 tags

Live values are illustrative.

Enterprise systems

Entered once, trusted everywhere

Quickflow reads from the systems that plan and record the work and writes back to the ones that act on it. Where it helps, the link runs both ways, so nobody keys the same material, person or result twice.

Quickflow

Two-way link

LIMS ⇄ Quickflow

Into Quickflow

Samples, test codes and specifications

Back to LIMS

Results, once a method goes routine

No interface? No code.

When a system has no API, Vision uses the screen

Plenty of validated lab software was never built to be connected. Quickflow Vision, the agent on each endpoint, works the application the way a trained person would. Someone who knows the system does the task once while Vision watches; every click and keystroke becomes a step.

Recorded, not programmed
No scripting skills and no change to the vendor’s software.
Runs only what was approved
Each job uses the approved script version and leaves a screenshot per step.
Reads as well as types
Values on an instrument’s own screen can be captured into the record.

Lab application · QC-GC-WS-01

User administrationMethodsReports

New user

UserRole

Save

Quickflow Vision · script

1Open “User administration”
2Type user name
3Pick role
4Click Save

Screenshot kept for every step.

Illustrative

GET /records/VAL-2026-031
 
200 OK
{
  "id": "VAL-2026-031",
  "status": "Approved",
  "signedBy": "R. Mehta",
  "version": "1.1"
}

APIs and events

Build the link only you can design

Some integrations are particular to your company: a dashboard of your own, an in-house planning tool, a data lake. Quickflow gives your developers the same doors it uses itself.

Connector set-up

Configure it, prove it works, then save

Every connector is set up the same way, whatever it speaks. Choose the protocol and how it signs in, press Test connection, watch real data arrive in the preview, and decide what is allowed out.

The sign-in each protocol expects
OAuth2, API keys, bearer tokens, client certificates (mutual TLS), SASL, Azure shared key and SAS, and AWS access keys.
Test connection before saving
A wrong address or credential shows up now, not at the first scheduled run.
Live streaming and data preview
See the actual records the connector will move before anything goes live.
Condition filters on outbound data
14 operators decide exactly which records leave Quickflow.

New connector · SOAP

Send and receive

NameLIMS results serviceEndpointhttps://lims.example/ResultService?wsdl

Sign-in method

OAuth2
API key
Bearer token
Client certificate (mTLS)
SASL
Azure shared key
Azure SAS
AWS access key

Connection OKSave

Live preview

SMP-24-0981Assay99.4 %
SMP-24-0982Assay98.9 %
SMP-24-0983Water (KF)0.31 %

Outbound filter

where status equals Approved

One condition of many · 14 operators

Illustrative names, addresses and values.

Governed connectors

Every connector change is on the record

An interface that moves GxP data is part of the validated system. Quickflow treats it that way: nothing about a connector changes without a trace, and nothing runs twice by accident.

Connector audit trail · LIMS results (SOAP)

Append-only

Connector created · LIMS results (SOAP)
2026-10-01 10:12 IST
A. Desai, IT
Connection tested · OK
2026-10-02 10:19 IST
A. Desai, IT
Activated
2026-10-03 10:26 IST
R. Mehta, QA
Retired
2026-10-04 10:33 IST
R. Mehta, QA
Reason (required): LIMS upgrade: old service switched off this weekend
Reinstated
2026-10-05 10:40 IST
R. Mehta, QA
Reason (required): Upgrade complete, endpoint revalidated

Illustrative entries. Entries can be added, never edited or deleted.

Retire and reinstate, never delete

A connector is retired rather than removed, and brought back the same way. Both need a reason, so an inspector can see why an interface stopped and why it started again.

One scheduled run, however many servers

When several application servers are running, each scheduled job still runs once. No duplicate records, no double posting to ERP.

One switch to pause every connector

For a maintenance window or an incident, an administrator turns connector execution off and back on. Connectors are running.

Quickflow to Quickflow

The applications already know each other

A method moves from the notebook to validation, a calculation into a routine template, a deviation into quality, without a connector to build. Add a second application and the link is already there.

Data integrity holds in transit

Captured at source

The value comes from the system that made it, never from someone’s notes.

Original time kept

Readings keep the timestamp the instrument or equipment recorded.

Every transfer audited

Who, what, when and from where, written to a read-only audit trail.

No second copy

Results move on by reference, so two systems never disagree about a number.

Questions

What IT and lab teams ask first

Which chromatography data systems do you connect to?

Empower, Chromeleon and OpenLab today. Results are taken from the processed result in the CDS, with the result version recorded, rather than typed in again.

Our equipment is old. Can it still be connected?

Usually, yes. PLCs and SCADA connect over OPC UA or Modbus TCP, building systems over BACnet/IP, and freezers, chambers and loggers over serial or network links through Quickflow Edge. If an instrument has no interface at all, Quickflow Vision reads the value from its own software screen.

What if a system has no API?

Quickflow Vision works the application through its screen, the way a trained person would. The task is recorded once by someone who knows the system, approved, and then run as that approved version, with a screenshot kept for every step.

Can our developers build their own integrations?

Yes. REST and GraphQL APIs, webhooks, database connections and data exports are available for links particular to your company, such as in-house tools, dashboards or a data lake. The details are set out for your IT team during evaluation.

Some of our systems only offer SOAP, MQTT or file drops. Is that a problem?

No. Connectors speak SOAP web services, MQTT and AMQP (for example RabbitMQ) in both directions, FTP and FTPS for files, and deliver data into your data lake on AWS (S3) or Azure (Data Lake Storage). Each signs in the way its protocol expects: OAuth2, API key, bearer token, client certificate (mutual TLS), SASL, Azure shared key or SAS, or AWS access key.

How are connector changes controlled?

Every change to a connector is written to an append-only audit trail. Connectors are retired and reinstated rather than deleted, and both need a reason. A connection is tested before it is saved, scheduled runs execute once even across several servers, and an administrator can switch connector execution off and on.

How do users sign in?

Through single sign-on with Active Directory, with role-based permissions on top in every Quickflow application.

Bring your systems to the pilot.

A fixed-price pilot: one live workflow, one team, six to eight weeks, connected to the instruments and systems that workflow really uses. You decide on the evidence.

Request a pilot Score your lab