# Data Connectors

IG ETL uses Data Connectors to manage access to external systems, such as SFTP servers and CRMs like HubSpot. Each connector has different requirements, so be sure to take a look at [the connector-specific documentation](#existing-data-connectors).

A data connector only manages access credentials and does not specify the exact records being accessed or modified. The exact records are instead specified on the workflow's configuration when the connector is selected. This allows the same connector to be used across multiple workflows—it can grant access to different files for different workflows from the same SFTP server, or write to different objects in a HubSpot instance, for example.

{% hint style="info" %}
Some data connectors may be "source only" or "destination only".
{% endhint %}

## Development vs. Production Credentials

A connector actually contains two sets of credentials—one for development purposes, and another for production uses. While Integration Gateway ETL does not enforce what type of system you enter credentials for, it is **strongly recommended** that you adhere to best practices and only enter SDLC-appropriate credentials.

## Existing Data Connectors

{% content-ref url="/pages/sZWn9jyyckrS5g2xxKAo" %}
[SFTP](/etl/data-connectors/sftp.md)
{% endcontent-ref %}

{% content-ref url="/pages/WbOR9m9h48m1PESMNklO" %}
[HubSpot](/etl/data-connectors/hubspot.md)
{% endcontent-ref %}

{% content-ref url="/pages/fX13KN2i45QLftAHjMjg" %}
[Salesforce](/etl/data-connectors/salesforce.md)
{% endcontent-ref %}

{% content-ref url="/pages/T2tO5XLU4wfrRKzFSsu7" %}
[Creatio](/etl/data-connectors/creatio.md)
{% endcontent-ref %}

{% content-ref url="/pages/rYagsv8v2hx368G4wONh" %}
[PostgreSQL](/etl/data-connectors/postgresql.md)
{% endcontent-ref %}

{% content-ref url="/pages/0KIvzz1pvJeLNGxSyyq5" %}
[Oracle SQL](/etl/data-connectors/oracle-sql.md)
{% endcontent-ref %}

{% content-ref url="/pages/LOdLQdmPNgw8jx1X9jlr" %}
[Amazon S3 Bucket](/etl/data-connectors/amazon-s3-bucket.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://glyue.docs.sandboxbanking.com/etl/data-connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.