SAP
Read and write approved business objects while SAP remains the system of record.
Connectors
These are the packaged connectors that ship now. Anything not on this list is reached through its own API, which is how most internal systems are connected in practice.
Business systems of record
Read and write approved business objects while SAP remains the system of record.
Customer, order, item, and financial records from NetSuite.
Customer, order, and operational records from Dynamics 365.
Worker and organizational records from Workday.
Accounts, contacts, opportunities, and custom objects from Salesforce.
Contacts, companies, and deals from HubSpot.
Commerce and payments
Products, orders, customers, and inventory from Shopify.
Customers, payments, and subscription records from Stripe.
Subscription, invoice, and billing records from Chargebee.
Invoice, payment, and ledger records from QuickBooks.
Data platforms and storage
Query Snowflake tables and views as a source for API products.
Query BigQuery datasets as a source for API products.
Read and write approved tables in a Postgres database.
Read structured files from an S3 bucket on a schedule.
Connect an internal warehouse as a governed source alongside the packaged platforms.
Treat a maintained sheet as a source, which is often how reference data actually lives.
Service, work, and messaging
Tickets and customer service history from Zendesk.
Issues and project records from Jira.
Deliver notifications and approvals into Slack channels.
Audience and campaign records from Mailchimp.
Send messages through Twilio as part of an approved operation.
Systems without a packaged connector
Any system with an API can be connected as a source, and your own applications' APIs are connected the same way. What a packaged connector adds is the mapping and the error handling we already maintain for that system.
The number of connected systems is set by your plan. We will confirm the coverage for your specific estate before you commit.