# Connector library (15+) — Use case > Database, Kafka, RabbitMQ, FTP, IBM MQ, file systems, and more — drag-and-drop task flows over the connectors that hold your enterprise together. *Developers · Integration · For developers* ## Fifteen-plus connectors. One task-flow surface. Apinizer's API Integrator turns enterprise connectors into drag-and-drop steps. Database, Kafka, RabbitMQ, FTP, IBM MQ, file systems, HTTP, SOAP, gRPC — all governed by the same gateway. [Five-minute quickstart](https://apinizer.com/developers/quickstart) · [Open API Integrator](https://apinizer.com/products/api-integrator) --- ## The problem *The problem* ### Most teams treat 'integration' as a tax they pay forever. Every new system needs a connector, an adapter, and a maintenance owner. Teams either buy a heavy iPaaS (and inherit a parallel ops stack) or hand-roll point-to-point integrations (and inherit a maintenance backlog). Apinizer's connector library makes integration a feature of the gateway: 15+ connectors, drag-and-drop task flows, one runtime, one audit. --- ## Capabilities ### Database connectors PostgreSQL, MySQL, MSSQL, Oracle, Db2, Mongo — read, write, stored procedures, with pooled connections and audit. ### Messaging connectors Kafka, RabbitMQ, IBM MQ, Solace — produce, consume, transform in the same task flow. Backpressure handled. ### File and protocol FTP / SFTP, file system, HTTP, SOAP, gRPC, email — every legacy and modern surface a connector. ### Drag-and-drop task flow Compose steps visually — read, transform, branch, fan-out, fan-in, write. Same designer engineers and analysts both use. ### Governed at the gateway Connector credentials in the encrypted vault. Each step audits. Rate limits and retries apply. ### As-code-ready Task flows ship as APIops manifests. Review in Git, apply through pipelines. --- ## Real-world examples ### Banking **Scenario:** Istanbul bank wires core banking to Kafka and partner SFTP **Outcome:** Task flow: pull from core, transform, fan-out to Kafka topic and partner SFTP. One designer, two destinations, one audit. ### Manufacturing **Scenario:** Stuttgart OEM streams MES events into 4 systems **Outcome:** Task flow consumes from Kafka, branches by event type, writes to ERP, data lake, partner API, and alerting. No separate integration product. ### Public sector **Scenario:** Stockholm agency lifts FTP file drops into a REST API **Outcome:** Connector watches an SFTP folder; task flow parses and exposes each record as a governed REST endpoint. Legacy partners keep dropping files; new partners get an API. ### Retail **Scenario:** Madrid retailer integrates POS and ERP through one task flow **Outcome:** POS pushes via HTTP; flow transforms; ERP receives via IBM MQ. Visual designer means store-ops engineers contribute changes. ### Insurance **Scenario:** Amsterdam insurer feeds claim events into a data lake + ML pipeline **Outcome:** Task flow consumes from RabbitMQ, decorates with policy data from PostgreSQL, writes to S3 and triggers a model retrain. ### Telecom **Scenario:** Milan carrier bridges legacy SOAP to modern partners via task flow **Outcome:** Inbound REST hits the gateway, flow transforms to SOAP, calls the legacy host, returns clean JSON. Modern partners never see SOAP. ### Energy **Scenario:** Prague utility ingests SCADA data into the analytics lake **Outcome:** Kafka connector consumes SCADA events; task flow enriches with topology data; writes to data lake and alarming surface in one pass. ### Government **Scenario:** Baku ministry routes citizen requests across 9 backend systems **Outcome:** One task flow per request type. Visual designer accepted by both engineers and policy analysts; changes ship in days, not quarters. --- ## Recommended modules - [API Integrator](https://apinizer.com/products/api-integrator) — Drag-and-drop task flows over the full connector library. - [API Gateway](https://apinizer.com/products/api-gateway) — Runtime that fronts every task flow with auth, rate limit, and audit. - [API Creator](https://apinizer.com/products/api-creator) — DB-2-API and Script-2-API integrate the same connectors as task flows. - [Analytics Engine](https://apinizer.com/products/analytics-engine) — Per-flow, per-step telemetry — see what each integration is doing. --- ## Resources - [Integrator overview](https://docs.apinizer.com/en) — Connectors, task flow primitives, governance behavior. - [API Integrator product](https://apinizer.com/products/api-integrator) — Drag-and-drop task flows; 15+ connectors. - [API Creator hub](https://apinizer.com/products/api-creator) — DB-2-API, Script-2-API, Mock API. - [Legacy modernization](https://apinizer.com/solutions/legacy-modernization) — What integration is really for — coexistence over rewrite. - [Analytics Engine](https://apinizer.com/products/analytics-engine) — Per-flow telemetry and audit join. - [Architecture overview](https://docs.apinizer.com/en/concepts/architecture) — Where Integrator and the connector library fit in the topology. --- ## Related use cases - [DB-2-API](https://apinizer.com/solutions/db-2-api) — For developers - [Script-2-API (Groovy / JS)](https://apinizer.com/solutions/script-2-api) — For developers - [Legacy modernization](https://apinizer.com/solutions/legacy-modernization) — For executives - [OpenAPI-first design](https://apinizer.com/solutions/openapi-first) — For developers --- ## Next step *Integration as a gateway feature* **Plug into anything. Govern at the gateway.** A 30-minute walkthrough — connectors, task flows, governance — on a Kubernetes of your choice. [Book a Demo](https://calendly.com/apinizer/15min) · [Read the docs](https://apinizer.com/developers/docs) --- ## Links - Products: https://apinizer.com/products - AI Gateway: https://apinizer.com/products/ai-gateway - Solutions: https://apinizer.com/solutions - Pricing: https://apinizer.com/pricing - Developers: https://apinizer.com/developers - Documentation: https://docs.apinizer.com/index-en - Blog: https://apinizer.com/blog - Contact: https://apinizer.com/company/contact © 2026 Apinizer. All rights reserved.