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

# Integrations overview

> How data gets into Allyy and how decisions get out

Allyy connects to your stack at both ends of the loop: **sources** bring data in, and **destinations** send decisions out. Many connectors do both.

## Bringing data in

You add these as data sources inside a dataset (see [Connect a data source](/processes/data)):

<CardGroup cols={2}>
  <Card title="Files" icon="file-csv">
    CSV and JSON — the simplest way to get started with an export from any system.
  </Card>

  <Card title="Warehouses & databases" icon="database">
    Google BigQuery and Microsoft SQL Server — connect directly to where your data already lives.
  </Card>

  <Card title="Storage & transfer" icon="folder-tree">
    Google Cloud Storage and SFTP — for scheduled file drops.
  </Card>

  <Card title="Marketing & CRM tools" icon="bullhorn">
    Agillic, ActiveCampaign and Salesforce — connect operational systems directly.
  </Card>
</CardGroup>

## Sending decisions out

Exported decisions can be synced to connected destinations or pulled via the API. See [Exporting decisions](/predictions/exporting).

## Connector guides

<CardGroup cols={2}>
  <Card title="Salesforce" icon="salesforce" href="/integrations/salesforce">
    Step-by-step setup of the Allyy.io Salesforce Connector, including the Connected App and credentials.
  </Card>

  <Card title="Content recommendations" icon="newspaper" href="/integrations/content_recommendation">
    Serve personalised content recommendations into your CMS (a separate recommender feature).
  </Card>
</CardGroup>

<Note>
  More connector guides will be added here. If you need a source or destination that isn't listed, contact [support@allyy.io](mailto:support@allyy.io) — many systems can be connected via files, SFTP, or a warehouse in the meantime.
</Note>