Connector roadmap.
Availability is stated per connector, and planned connectors are not yet implemented. Nothing on this page claims a partnership. When a connector ships, its state changes here and an entry appears in the changelog.
Categories
36 connectors shown
- Custom APIPlanned
Custom REST API
REST · API key / OAuth 2.0 / basic
Any REST endpoint: declare the base URL, auth, pagination style and the response path. Cursor field configurable for incremental sync.
- Custom APIPlanned
Custom GraphQL API
GraphQL · bearer token
Query documents with variables, mapped from the response data path.
- Custom APIPlanned
Webhook receiver
Inbound HTTPS · HMAC
Accept inbound events as a flow trigger with signature verification.
- Custom APIPlanned
SFTP / file drop
SFTP · key or password
CSV and JSONL files with a declared schema and an archive-on-success policy.
- DatabasePlanned
PostgreSQL
Direct · TLS · read/write
Table and view sources, upsert on a key, schema discovery with type mapping.
- DatabasePlanned
MySQL
Direct · TLS · read/write
Table sources with cursor-based incremental reads and batched upserts.
- DatabasePlanned
Microsoft SQL Server
Direct · TLS · read/write
Table and stored-procedure sources; batched writes with transaction control.
- DatabasePlanned
MongoDB
Direct · TLS · read/write
Collection sources with projection, and upsert on a document key.
- DatabasePlanned
Snowflake
Direct · key-pair auth
Warehouse destination with staged batch loads.
- DatabasePlanned
BigQuery
Service account
Dataset destination with schema-mapped streaming inserts.
- CRMPlanned
Salesforce
REST · OAuth 2.0
Standard and custom objects, field discovery, updated-at cursors, bulk read path.
- CRMPlanned
HubSpot
REST · OAuth 2.0
Contacts, companies and deals with association handling.
- CRMPlanned
Zoho CRM
REST · OAuth 2.0
Modules and custom fields with region-aware endpoints.
- CRMPlanned
Microsoft Dynamics 365
OData · OAuth 2.0
Entity sets with OData filtering and delta links.
- CRMPlanned
Pipedrive
REST · API token
Persons, organizations and deals.
- CRMPlanned
Freshsales
REST · API key
Leads and contacts with custom field mapping.
- ERPPlanned
SAP S/4HANA
OData · OAuth 2.0 / basic
Business partner, material and sales document services.
- ERPPlanned
Oracle NetSuite
SuiteTalk REST · OAuth 1.0a
Records and saved searches with field-level mapping.
- ERPPlanned
Odoo
XML-RPC / REST · API key
Models and fields discovered from the instance.
- ERPPlanned
Microsoft Business Central
OData · OAuth 2.0
Customers, items and orders.
- ERPPlanned
Tally
XML over HTTP · local gateway
Ledgers and vouchers via the Tally XML gateway.
- ERPPlanned
Zoho Books
REST · OAuth 2.0
Invoices, contacts and items.
- CommercePlanned
Shopify
Admin REST/GraphQL · OAuth
Orders, products, inventory and customers; webhook triggers on order events.
- CommercePlanned
WooCommerce
REST · key/secret
Orders and products with line-item flattening.
- CommercePlanned
Magento / Adobe Commerce
REST · bearer token
Orders, catalogue and stock items.
- CommercePlanned
Amazon Selling Partner
SP-API · LWA OAuth
Orders and inventory reports with rate-limit aware reads.
- CommercePlanned
Razorpay
REST · key/secret
Payments and settlements as read-only sources.
- CommercePlanned
Stripe
REST · restricted key
Customers, invoices and payment intents.
- StoragePlanned
Amazon S3
IAM role / access key
Object sources and destinations with prefix partitioning.
- StoragePlanned
Google Cloud Storage
Service account
Bucket objects as CSV, JSONL or Parquet.
- StoragePlanned
Azure Blob Storage
SAS / service principal
Container objects with a declared schema.
- StoragePlanned
Google Sheets
Sheets API · OAuth 2.0
Ranges as tabular sources, for operational hand-maintained data.
- CommunicationPlanned
Slack
Web API · OAuth 2.0
Channel notifications for flow and alert events.
- CommunicationPlanned
Microsoft Teams
Graph · OAuth 2.0
Channel messages for operational alerts.
- CommunicationPlanned
SMTP email
SMTP · TLS
Alert and digest delivery to an operations mailbox.
- CommunicationPlanned
Twilio
REST · key/secret
SMS notification destination for failure alerts.
The honest answer to “do you support X”
Any REST or GraphQL endpoint, and databases over a secured connection.
A custom connector is declared, not coded: base URL, auth method, pagination style, the response path to the records, and the field to use as an incremental cursor. It is the connector most integrations actually need.
Auth
API key, bearer token, basic auth, OAuth 2.0 client credentials and authorization code.
Pagination
Page number, offset, cursor, or a next-link in the response body.
Cursor
Any monotonic field — updated_at, a sequence, or a provider-supplied cursor.
Rate limits
Declare the upstream limit and the worker respects it instead of discovering it with 429s.
Sequencing
A connector changes state only when it actually ships.
The first connectors are the ones that need no third-party partnership: PostgreSQL, MySQL, custom REST, and file drop. SaaS connectors requiring OAuth review follow. This page, the changelog and the product move together.