Connectors
Source and destination connectors available in Portlane
Portlane connects to the systems integration teams already operate. Connectors cover common databases, APIs, files, and streams.
Categories
| Category | Examples |
|---|---|
| Databases | PostgreSQL, SQL Server, Oracle, MySQL |
| Files | Local folders, SMB shares, S3-compatible object storage |
| APIs | REST, GraphQL, OData |
| Streams | Kafka, MQTT, webhooks |
| SaaS | Common CRM, ERP, and ticketing endpoints (catalog expands per release) |
Systems with no API
Some web applications — legacy CRMs, supplier portals, internal tools — don't expose an API, a database, or a file interface a connector can target. For that case, the Portlane ecosystem is extending a complementary RPA module: a browser automation agent that records a person's actions once and runs them again, delivering the resulting data to Portlane the same way a connector would.
Capabilities
Each connector supports a subset of:
- Read — Poll or receive new data via webhook
- Write — Push transformed data to a target endpoint
- Schema — Map source fields into the flux's canonical record
Not every connector supports every mode — check the reference for your specific system.
Custom connectors
Teams extend Portlane with pure Python transforms for proprietary systems, versioned in portlane-flux alongside standard connectors.
Detailed reference
Connector-specific configuration (auth modes, rate limits, field mappings) is documented in the customer tier of this documentation, available in your on-prem Tour de contrôle bundle after installation.