Connector scope and deferred targets
This catalog focuses on source extraction patterns that can be implemented as Vortexify connectors and syncs. Deferred entries record integrations that need a different access or ingestion design.
The current focus is bounded source reads from APIs, databases, and storage. Kafka-style record streaming and Flink-based execution are outside the supported scope. Model inference/actions and webhook message ingestion need their own integration design.
The targets below remain in the structured catalog so they are not silently lost. Deferred does not generally mean technically impossible.
| Target | Why it is deferred |
|---|---|
| WhatsApp Business | Message ingestion needs a durable webhook receiver; outside the current polling-source collection. |
| Lattice | Hold pending an approved third-party authorization model. |
| Dext | Hold pending confirmation of the product and receipt/invoice extraction endpoints. |
| Digital River | Hold pending current service and onboarding confirmation. |
| Sendle | Shipping operations ceased; exclude from active integration targets. |
| Evernote | Hold pending validation of the beta MCP interface for unattended extraction. |
| Confluent | Record-stream consumption is outside the current connector scope. |
| Apache Kafka | Record streaming is outside the current connector scope. |
| OpenAI | The supplied target describes model inference; document separately from source extraction. |
| Anthropic Claude | The supplied target describes model inference; the existing administrative-data template does not implement that capability. |
| Azure OpenAI | The supplied target describes model inference; document separately from source extraction. |
| Cohere | The supplied target describes model inference/reranking; document separately from source extraction. |
| Replicate | The supplied target describes model inference; document separately from source extraction. |
Access-gated sources
Paid API access, customer permissions, enabled product modules, and customer-managed networking do not automatically exclude a source. The relevant guides describe these prerequisites. A documentation page or installed driver does not establish that a particular account can access every resource.
What a guide provides
These are implementation references to adapt to the requested dataset. The overview lists useful dataset possibilities; the example teaches one access/extraction pattern. Its scope can be a full read, a page, a query, a report, or a request recipe requiring deployment-specific inputs. Use the Custom API guide for SDK structure and the selected source documentation for its actual auth, schemas, pagination, and limits.
Use Custom API as the general starting point when a source-specific pattern does not fit. Examples have not all been exercised with live vendor credentials.
Return to the connector index.