Integrations
Connect the systems your business already relies on.
Darwin brings their data together through existing integrations and scoped connections built around your needs.
Integration coverage
Existing capabilities. Defined scope.
Coverage depends on the objects, permissions and workflow agreed for your business. Implemented capability does not imply blanket support for every customer or source-system feature. Scheduled syncs below describe connection patterns, not service commitments.
| Named system | Objects | Direction | Sync or trigger | Auth | Support status | Productized vs custom | Maintainer |
|---|---|---|---|---|---|---|---|
| Existing capabilities | |||||||
| Microsoft 365 / Entra / Teams | Mail, attachments, identity, hierarchy, approval interactions | Inward; replies, PO emails and approvals outward | Mail events and business actions; scheduled intake and hierarchy sync | OAuth application credentials or managed identity; Teams JWT | Implemented for configured workflows | Reusable transport; customer-specific permissions and mappings | Darwin |
| BILL through iBuy | Vendors, GL/project codes, bills, payment status, attachments, credits | Inward; approved invoices and credits outward | Scheduled master/status sync; approval or manual bill push | BILL session credentials with organization/developer key | Implemented; outbound writes gated; payments stay in BILL | Existing iBuy connector; configured per engagement | Darwin |
| Supplier PunchOut / cXML | Catalogs, carts, POs, changes, confirmations, ship notices, invoices | Supplier exchange inward and outward | Interactive and business events; scheduled retries | Per-supplier identities and shared secrets | Implemented protocol adapter; supplier coverage confirmed individually | Reusable adapter; customer-specific supplier configuration | Darwin |
| ADP | Employees, payroll and recruiting; WFM payroll CSV | API reads inward; payroll file generation outward | Scheduled data sync; payroll export on action | OAuth client credentials and mutual TLS for API reads | Payroll CSV export; delivery scoped separately | Reusable client; configured workforce projections | Darwin |
| Dropbox | Files, folders and documents | Inward; document uploads outward | Request-driven access; scheduled monitoring | OAuth refresh token or access-token fallback | Implemented connector and configured monitoring | Reusable connector; BCI-specific finance workflows | Darwin |
| Linear / ITSM | Tickets, comments and status updates | Outward; webhook updates inward | Events and scheduled outbox delivery | API key and webhook secret | Implemented support lifecycle synchronization | Existing configurable support integration | Darwin |
| Google through Finch | Gmail messages and labels; Google Tasks | Mailbox reads inward; label and task updates outward | Scheduled, event-driven and user-driven workflows | OAuth | Implemented Gmail and Google Tasks coverage | Existing Finch workflows; not all Google services | Darwin |
| Scoped customer workflows | |||||||
| VIP / KARMA | Account sales, case equivalents, visits and account notes | Inward | Scheduled browser report extraction; on-demand CSV/PDF uploads | Portal login; Darwin access for uploads | Implemented reporting workflow; not a vendor API | Customer-specific workflow | Darwin |
| Nielsen reports | Retail dollar/unit sales, prior-year comparisons, account/chain matching | Inward | On-demand spreadsheet report upload | Darwin upload access | Implemented file import; not a direct Nielsen API connection | Existing report import; configured report formats | Darwin |
| TrackTik | Clients, contracts, positions, pay/bill data, shifts, employee rate entries | Inward; scoped missing pay/bill matrix entries outward | Scheduled shift/reference sync and matrix updates | OAuth password grant | Implemented client and pipelines | Reusable client; current mappings and writes are BCI-specific | Darwin |
| Azure warehouse / database exchange | Cleaned compliance snapshots, identity mappings, employee records | Warehouse data inward; configured employee receiver outward | Scheduled compliance sync; receiver events and catch-up | Database credentials with TLS; receiver shared secret | Implemented warehouse and receiver contracts | Customer-specific data exchange | Darwin |
| CourseStorm | Courses, students and registrations | Inward to the BCI Azure warehouse | Daily API ingestion | Basic Auth | Implemented upstream API integration | Customer-specific BCI data-platform integration | Darwin, within the BCI data platform |
| Smartsheet | Sheets and rows | Inward to BCI Azure; Darwin consumes warehouse results | Daily API ingestion | Bearer token | Implemented upstream API integration | Customer-specific BCI data-platform integration | Darwin, within the BCI data platform |
| Pending activation | |||||||
| Plaid | Detailed scope confirmed before activation | Confirmed before activation | Confirmed before activation | Confirmed before activation | Connection established; not yet in use | Pending activation; coverage confirmed per engagement | Darwin, within agreed scope |
| QuickBooks | Detailed scope confirmed before activation | Confirmed before activation | Confirmed before activation | Confirmed before activation | Coming soon / in rollout; no fixed launch date | Pending activation; coverage confirmed per engagement | Darwin, within agreed scope |
Existing capabilities
Microsoft 365 / Entra / TeamsImplemented for configured workflows
- Objects
- Mail, attachments, identity, hierarchy, approval interactions
- Direction
- Inward; replies, PO emails and approvals outward
- Sync or trigger
- Mail events and business actions; scheduled intake and hierarchy sync
- Auth
- OAuth application credentials or managed identity; Teams JWT
- Productized vs custom
- Reusable transport; customer-specific permissions and mappings
- Maintainer
- Darwin
BILL through iBuyImplemented; outbound writes gated; payments stay in BILL
- Objects
- Vendors, GL/project codes, bills, payment status, attachments, credits
- Direction
- Inward; approved invoices and credits outward
- Sync or trigger
- Scheduled master/status sync; approval or manual bill push
- Auth
- BILL session credentials with organization/developer key
- Productized vs custom
- Existing iBuy connector; configured per engagement
- Maintainer
- Darwin
Supplier PunchOut / cXMLImplemented protocol adapter; supplier coverage confirmed individually
- Objects
- Catalogs, carts, POs, changes, confirmations, ship notices, invoices
- Direction
- Supplier exchange inward and outward
- Sync or trigger
- Interactive and business events; scheduled retries
- Auth
- Per-supplier identities and shared secrets
- Productized vs custom
- Reusable adapter; customer-specific supplier configuration
- Maintainer
- Darwin
ADPPayroll CSV export; delivery scoped separately
- Objects
- Employees, payroll and recruiting; WFM payroll CSV
- Direction
- API reads inward; payroll file generation outward
- Sync or trigger
- Scheduled data sync; payroll export on action
- Auth
- OAuth client credentials and mutual TLS for API reads
- Productized vs custom
- Reusable client; configured workforce projections
- Maintainer
- Darwin
DropboxImplemented connector and configured monitoring
- Objects
- Files, folders and documents
- Direction
- Inward; document uploads outward
- Sync or trigger
- Request-driven access; scheduled monitoring
- Auth
- OAuth refresh token or access-token fallback
- Productized vs custom
- Reusable connector; BCI-specific finance workflows
- Maintainer
- Darwin
Linear / ITSMImplemented support lifecycle synchronization
- Objects
- Tickets, comments and status updates
- Direction
- Outward; webhook updates inward
- Sync or trigger
- Events and scheduled outbox delivery
- Auth
- API key and webhook secret
- Productized vs custom
- Existing configurable support integration
- Maintainer
- Darwin
Google through FinchImplemented Gmail and Google Tasks coverage
- Objects
- Gmail messages and labels; Google Tasks
- Direction
- Mailbox reads inward; label and task updates outward
- Sync or trigger
- Scheduled, event-driven and user-driven workflows
- Auth
- OAuth
- Productized vs custom
- Existing Finch workflows; not all Google services
- Maintainer
- Darwin
Scoped customer workflows
VIP / KARMAImplemented reporting workflow; not a vendor API
- Objects
- Account sales, case equivalents, visits and account notes
- Direction
- Inward
- Sync or trigger
- Scheduled browser report extraction; on-demand CSV/PDF uploads
- Auth
- Portal login; Darwin access for uploads
- Productized vs custom
- Customer-specific workflow
- Maintainer
- Darwin
Nielsen reportsImplemented file import; not a direct Nielsen API connection
- Objects
- Retail dollar/unit sales, prior-year comparisons, account/chain matching
- Direction
- Inward
- Sync or trigger
- On-demand spreadsheet report upload
- Auth
- Darwin upload access
- Productized vs custom
- Existing report import; configured report formats
- Maintainer
- Darwin
TrackTikImplemented client and pipelines
- Objects
- Clients, contracts, positions, pay/bill data, shifts, employee rate entries
- Direction
- Inward; scoped missing pay/bill matrix entries outward
- Sync or trigger
- Scheduled shift/reference sync and matrix updates
- Auth
- OAuth password grant
- Productized vs custom
- Reusable client; current mappings and writes are BCI-specific
- Maintainer
- Darwin
Azure warehouse / database exchangeImplemented warehouse and receiver contracts
- Objects
- Cleaned compliance snapshots, identity mappings, employee records
- Direction
- Warehouse data inward; configured employee receiver outward
- Sync or trigger
- Scheduled compliance sync; receiver events and catch-up
- Auth
- Database credentials with TLS; receiver shared secret
- Productized vs custom
- Customer-specific data exchange
- Maintainer
- Darwin
CourseStormImplemented upstream API integration
- Objects
- Courses, students and registrations
- Direction
- Inward to the BCI Azure warehouse
- Sync or trigger
- Daily API ingestion
- Auth
- Basic Auth
- Productized vs custom
- Customer-specific BCI data-platform integration
- Maintainer
- Darwin, within the BCI data platform
SmartsheetImplemented upstream API integration
- Objects
- Sheets and rows
- Direction
- Inward to BCI Azure; Darwin consumes warehouse results
- Sync or trigger
- Daily API ingestion
- Auth
- Bearer token
- Productized vs custom
- Customer-specific BCI data-platform integration
- Maintainer
- Darwin, within the BCI data platform
Pending activation
PlaidConnection established; not yet in use
- Objects
- Detailed scope confirmed before activation
- Direction
- Confirmed before activation
- Sync or trigger
- Confirmed before activation
- Auth
- Confirmed before activation
- Productized vs custom
- Pending activation; coverage confirmed per engagement
- Maintainer
- Darwin, within agreed scope
QuickBooksComing soon / in rollout; no fixed launch date
- Objects
- Detailed scope confirmed before activation
- Direction
- Confirmed before activation
- Sync or trigger
- Confirmed before activation
- Auth
- Confirmed before activation
- Productized vs custom
- Pending activation; coverage confirmed per engagement
- Maintainer
- Darwin, within agreed scope
Cloud and data platforms
Bring the data foundation together.
Darwin's AWS and Azure experience spans data pipelines, centralized data platforms, orchestration, access controls and ongoing operations. We scope the cloud and data-platform work around the connections your business needs.
Scope and ownership
Agree the connection before delivery.
Darwin maintains its platform and agreed integrations. You control source systems, authorized access, source data and approvals. Support and maintenance are scoped per engagement.
Configuration adapts existing capability. Custom connections and implementation work are scoped separately; source licensing, API limits and data quality can affect delivery.
Ariba invoice CSV, distributor reports and bank-statement CSV/OFX/QFX are scoped file exchange, rather than direct vendor or live banking connections.