BergLabs.

Integrations

Connected to the systems you already run.

BergFlow and BergAuto connect to email, documents, voice, CRM, ERP and databases, so the record and the review layer sit on top of your stack instead of replacing it.

Discuss an integration See use cases
Integration mapConnect · Read · Act · Record
  • Read and writeEmail and messaging
  • Read and writeDocuments
  • Read and writeVoice
BergAutoActs through APIsScored, with wait states
GateWrites that matter waitMoney, access, commitments
BergFlowRecords every syncTime, source, outcome
  • Read and writeCRM and support
  • Read and writeERP
  • Read and writeDatabases and IT systems
Illustrative diagram. Reads and writes run through the layer. Writes that change money, access or customer commitments wait for a person.
  • Read

    Pull work in from the systems where it arrives.

  • Act

    Write results back through APIs and webhooks.

  • Record

    Every sync and action logged in BergFlow.

Integration families

Six families, and the systems BergFlow and BergAuto connect to.

  • Email and messaging

    Shared inboxes, outreach sequences and team chat, read in and written back.

    • Intercom
    • Outreach
    • Apollo
    • Slack
    • Zendesk
    • Gmail
    • Outlook
    • Microsoft Teams
    • Front

  • Documents

    Contracts, forms, evidence packs and knowledge bases, extracted and filed.

    • DocuSign
    • Ironclad
    • Drive
    • Word
    • Notion
    • OneTrust
    • Logikcull
    • SharePoint
    • Box
    • Adobe Acrobat Sign

  • Voice

    Call platforms whose recordings and dispositions feed the record.

    • Aircall
    • Genesys
    • Twilio
    • Five9
    • Talkdesk
    • Amazon Connect
    • RingCentral
    • Dialpad

  • CRM and support

    Accounts, leads, tickets and campaigns, kept clean and routed.

    • Salesforce
    • HubSpot
    • Marketo
    • ZoomInfo
    • Clari
    • Freshdesk
    • Shopify
    • Pipedrive
    • Gong

  • ERP, finance and HR

    Invoices, payments, approvals and people records, matched and approved.

    • NetSuite
    • SAP
    • Stripe
    • Coupa
    • BlackLine
    • Expensify
    • Workday
    • BambooHR
    • QuickBooks
    • Xero

  • Databases and IT systems

    Databases, warehouses and IT systems of record, read and updated through secure connectors.

    • ServiceNow
    • Jira
    • Okta
    • Jamf
    • Datadog
    • CrowdStrike
    • Greenhouse
    • Lever
    • Lattice

Systems listed are ones BergLabs has connected in use cases. Names are trademarks of their owners and do not imply a partnership or endorsement.

REST & GraphQL API

Direct API integration, governed end to end.

Direct API integration with OAuth 2.0, key-based auth and webhook listeners. Real-time bi-directional sync with retry logic and rate-limit handling.

  • OAuth 2.0 or key-based authentication, scoped per project
  • Webhook listeners for events from your systems
  • Bi-directional sync with retries and backoff
  • Rate limits respected per system
Connection C-07Auth · Event · Act · Log
  1. AuthOAuth 2.0 token, project scopeLeast privilege
  2. EventWebhook: invoice.createdReceived and queued
  3. ActMatch and write backWaits if the amount is over limit
  4. LogSync recorded in BergFlowTime, source, outcome
Illustrative connection. Endpoints, scopes and limits are agreed with your technical team.

How a connection is governed

Every connection runs under the same four rules.

The integration is part of the workflow, so it carries the workflow’s controls.

  1. 01Scoped credentials

    Each connection uses credentials scoped to the project and the actions agreed, nothing broader.

  2. 02Logged syncs

    Every read and write is logged in BergFlow with the time, the source and the outcome.

  3. 03Human gates on consequential writes

    Writes that change money, access or customer commitments wait at a review gate for a named person.

  4. 04Retries and rate limits

    Failed syncs retry with backoff, and each system’s rate limits are respected.

Questions

Questions about integrations

Systems, authentication and what happens without an API.

Integrations

Do you replace our systems?

No. BergFlow and BergAuto connect to the systems you already run and keep them as the systems of record. There is no rip and replace.

Which systems can you connect?

Email and messaging, documents, voice, CRM and support, ERP, finance and HR, and databases and IT systems. The cards above list systems we have connected in use cases.

Are these partnerships?

No. The systems named are ones BergLabs has connected in use cases. Names are trademarks of their owners and do not imply a partnership.

How do you authenticate?

With OAuth 2.0 or key-based authentication scoped to the project, plus webhook listeners for events.

What if a system has no API?

Work can move through email, document exports or a reviewed manual step, recorded in BergFlow like any other action.

Map your stack with us.

List the systems a workflow touches. We show you where the layer reads, where it writes and where a person signs off.

Discuss an integration Read the documentation