> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apinizer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> You can use connectors used in Task Flows and API traffic log management in Apinizer to perform integration components for database, message queues, email, file transfer, and logging operations. Connectors can connect to different systems, send data to these systems, or retrieve data from these systems.

<Info>
  Connectors are used in two main areas: creating workflows in **Task Flows** (API Integrator) and sending API traffic logs to different systems in **Gateway Environments**. Each connector is customized to communicate with a specific system or protocol and can be easily used with form-based configuration without the need to write code.
</Info>

## Module's Core Components

The Connectors module forms the foundation of integration and automation operations on the Apinizer platform. With this module:

<CardGroup cols={2}>
  <Card title="Task Flow Integrations" icon="puzzle-piece">
    You can establish connections to different systems in Task Flows and exchange data.
  </Card>

  <Card title="API Traffic Log Management" icon="file-lines">
    You can route API traffic logs to different target systems.
  </Card>

  <Card title="Data Operations" icon="database">
    You can perform database operations, message queue operations, and file transfers.
  </Card>

  <Card title="Communication and Logging" icon="envelope">
    You can configure email sending, notification, and logging operations.
  </Card>
</CardGroup>

## Connector Types

Connectors are categorized according to their usage areas as follows:

### Database and Data Processing Connectors

<CardGroup cols={3}>
  <Card title="Database" icon="database" href="/en/integrations/connectors/database-connector">
    Establishing connections to SQL databases, running queries, and performing database operations. MySQL, PostgreSQL, Oracle, MSSQL, DB2 support.
  </Card>

  <Card title="Elasticsearch" icon="magnifying-glass" href="/en/integrations/connectors/elasticsearch-connector">
    Performing data indexing, search queries, and Elasticsearch operations using Elasticsearch connection definitions.
  </Card>

  <Card title="Script" icon="code" href="/en/integrations/connectors/script-connector">
    Performing programmatic operations using Groovy or JavaScript and adding custom business logic to processes.
  </Card>
</CardGroup>

### Message Queue Connectors

<CardGroup cols={3}>
  <Card title="Kafka" icon="layer-group" href="/en/integrations/connectors/kafka-connector">
    Message sending and receiving operations with Apache Kafka integration. Message queue management for event-driven architectures.
  </Card>

  <Card title="RabbitMQ" icon="inbox" href="/en/integrations/connectors/rabbitmq-connector">
    Message queue operations and asynchronous messaging with RabbitMQ integration.
  </Card>

  <Card title="ActiveMQ" icon="server" href="/en/integrations/connectors/activemq-connector">
    Message broker operations and message queue management with Apache ActiveMQ integration.
  </Card>
</CardGroup>

### HTTP and API Connectors

<CardGroup cols={3}>
  <Card title="API Call" icon="globe" href="/en/integrations/connectors/api-call-connector">
    Triggering API endpoints, retrieving data, and sending data to other endpoints. HTTP/REST API calls.
  </Card>

  <Card title="Webhook" icon="plug" href="/en/integrations/connectors/webhook-connector">
    Performing webhook listening, sending, and event-driven operations using webhook connection definitions.
  </Card>
</CardGroup>

### File Transfer Connectors

<CardGroup cols={2}>
  <Card title="FTP Read" icon="file-arrow-down" href="/en/integrations/connectors/ftp-read-connector">
    Performing file search, reading, and content retrieval in different formats using FTP connection definitions.
  </Card>

  <Card title="FTP List" icon="list" href="/en/integrations/connectors/ftp-list-connector">
    File listing and directory structure viewing operations on FTP servers.
  </Card>
</CardGroup>

### Communication and Notification Connectors

<CardGroup cols={2}>
  <Card title="Email Sending" icon="envelope" href="/en/integrations/connectors/email-connector">
    Sending emails in error situations, email configuration, and variable usage. SMTP server configuration.
  </Card>

  <Card title="Notification" icon="bell" href="/en/integrations/connectors/notification-connector">
    Sending notifications to users when job definitions run and managing notifications from the application interface.
  </Card>
</CardGroup>

### Logging and Monitoring Connectors

<CardGroup cols={3}>
  <Card title="Syslog" icon="file-lines" href="/en/integrations/connectors/syslog-connector">
    Sending log messages with Syslog protocol and centralized log management.
  </Card>

  <Card title="Logback" icon="file-code" href="/en/integrations/connectors/logback-connector">
    Sending log records and log management with Logback framework.
  </Card>

  <Card title="SNMP" icon="network-wired" href="/en/integrations/connectors/snmp-connector">
    Sending traps and network monitoring operations with SNMP protocol.
  </Card>
</CardGroup>

### System Connectors

<CardGroup cols={1}>
  <Card title="Linux Script" icon="terminal" href="/en/integrations/connectors/linux-script-connector">
    Running Linux commands and performing system-level operations.
  </Card>
</CardGroup>

<Tip>
  **Elasticsearch Connector** is particularly important. Querying and analytically visualizing API Traffic in Apinizer Management Console is only possible by adding Elasticsearch Connector to the relevant environment. Without Elasticsearch Connector, analytics screens, API Traffic tabs, and report generator menus cannot be used.
</Tip>

<Warning>
  When connectors are used in Gateway Environments, the structure and privacy settings of API traffic logs are important. API Proxy Traffic Privacy Settings should be configured so that sensitive data does not appear explicitly in log records.
</Warning>