Optic platform / Sources

Connect the systems behind the work.

Optic connects CRMs, ERPs, spreadsheets, forms, inboxes, shared drives, databases, and internal tools so teams, dashboards, automations, and AI workflows start with the full operating picture.

Connector coverage

Built for the software your team already uses.

Optic supports 200+ common connector patterns across modern business software, databases, documents, inboxes, spreadsheets, and workflow tools. When a system is older or highly customized, we can still integrate through APIs, databases, flat files, SFTP, webhooks, EDI, or managed legacy handoffs.

QuickBooksSalesforceNetSuiteMicrosoft DynamicsHubSpotShopifyStripeServiceTitanSageSAPWorkdayADPJiraAsanamonday.comMicrosoft 365Google WorkspaceSlack

ERP and accounting

Orders, invoices, inventory, payments, vendor records, job costing, and financial details.

CRM and sales

Accounts, contacts, deals, activities, follow-ups, service history, and customer context.

Projects and operations

Tasks, jobs, schedules, field notes, approvals, status updates, and service workflows.

Time, payroll, and people

Timesheets, labor details, employee records, approvals, and staffing information.

Documents and inboxes

PDFs, forms, emails, shared drives, spreadsheets, and repeated intake documents.

Legacy and custom systems

Older databases, file drops, exports, custom portals, internal software, and systems without clean modern APIs.

What it connects

Connected Sources is built for the systems that hold the real workflow picture.

Most teams do not have one clean system of record. Optic connects the places where the work already lives, then prepares that information for workflow tools, reports, reviews, AI, automation, and system updates.

  • CRM, ERP, accounting, project, inventory, and service systems
  • Spreadsheets, shared drives, inboxes, forms, and internal tools
  • Databases, exports, webhooks, APIs, file drops, and legacy handoffs
  • Customer, order, job, asset, status, approval, and activity records

What gets prepared

The goal is usable context, not just another integration.

Optic maps the fields, owners, timing, and rules around each source so the workflow has the right information before software, reporting, AI, or automation touches it.

  • Source-to-source field mapping
  • Record matching and duplicate checks
  • Business rules, ownership, and workflow timing
  • Clean context packets for dashboards, reviews, AI, automation, and reporting

Supported over time

We keep the connections aligned as systems and workflows change.

Connectors are not set-and-forget. Fields change, APIs update, exports drift, and business rules evolve. Optic is maintained so the information layer keeps working.

  • Connector monitoring and troubleshooting
  • Field and workflow mapping updates
  • Legacy integration support
  • Data quality checks and exception handling

Source coverage

Modern tools, legacy systems, documents, and inboxes can all feed the workflow.

Connected Sources gives buyers confidence that Optic can meet their environment where it is instead of forcing a rip-and-replace project.

Temporary Optic connected sources visual showing business systems feeding a workflow layer
sourceERP

Orders, inventory, vendors, invoices, status

sourceCRM

Accounts, contacts, deals, notes, follow-ups

sourceAccounting

Payments, invoices, POs, job costing

sourceProject tools

Tasks, schedules, approvals, status updates

sourceInboxes

Requests, attachments, handoffs, approvals

sourceDatabases

Custom records, exports, IDs, history

sourceLegacy systems

Flat files, SFTP, EDI, custom portals

sourceShared drives

Documents, spreadsheets, packets, reports

How it works

Connected Sources inside the Optic workflow.

A connected information layer that helps every system, workflow, report, and AI process speak the same language while keeping people from copying data between tools.

Map the source systems

Identify where the workflow data lives and which system should own each record.

Connect the required fields

Pull the information the workflow needs without forcing teams into a full platform replacement.

Prepare usable context

Normalize records, summaries, and handoffs so teams, dashboards, automations, and AI workflows can use the same trusted information.

Next step

Want to see where connected sources fits?

Show us the workflow, document, system handoff, or repeated decision you want agents to support.