Skip to main content

Business systems integrations

Reference selected CRM, e-signature and registry records in Seal, or scope API connections to other business systems.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

What these systems hold.

Business systems hold the records around regulated work: signed agreements, customer and supplier accounts, support tickets, IT incidents and change requests, registry entities and purchasing data.

Some of these become GxP evidence. A complaint may first arrive as a support ticket, and FDA’s drug GMP regulations require a written record of each complaint, with quality review of any that suggests a product failed its specification (21 CFR 211.198). A supplier review may start from the CRM account and the signed quality agreement.

What Seal reads and writes back.

DocuSign, Salesforce, Benchling, Dynamics 365, ServiceNow and Zendesk are organisation libraries: an admin selects the records, Seal reads captured versions, and nothing is written to the source system, which stays the source of truth. QuickBooks is different: purchase orders and vendor records can move both ways through a connection set up with Seal’s API or Scripts, and which system owns each record is agreed first. QuickBooks Online and Desktop have different interfaces.

Seal
  1. DocuSign, Salesforce, Benchling and 3 moreSource of truth

    Reads Captured versions of selected records

  2. QuickBooksSource of truth agreed when scoped

    Reads Purchase orders, vendor records and related financial data

    Writes back The purchase-order and vendor data you agree

7 connections

Blueprints that use these records.

Start with one source.

Tell us what Neil needs to do and where the records live. We’ll scope the connection with your team.

Book a demo