Skip to main content
Connectors copy data from a source, such as a MySQL database or a hosted JSON file, into an Algolia index. You configure them in the Algolia dashboard or with the Ingestion API.

​
Why use connectors

A connector replaces the ingestion pipeline you would otherwise write and operate yourself:
  • Algolia hosts the ingestion service. The schedule, the retries, and the run history all run in Algolia.
  • Transformations run in Algolia. Use no-code transformations or JavaScript to change your records. Preview the result in the Algolia dashboard. No separate service between your source and your index.
  • Credentials stay in Algolia. Store the credentials for a source once, then reuse them across tasks.
  • Failures are visible without extra tooling. The Connector Debugger shows the status of each run, and Algolia emails you about repeated failures.
  • Anyone on your team can make changes. The schedule, the indexing strategy, and the transformations are dashboard fields, so a colleague can adjust them without a deployment.

​
Available connectors

​
How connectors work

Connectors have these parts:
  • Sources define where your data comes from, such as a JSON file on your server, or a MySQL database.
  • Destinations define where your data goes, such as an Algolia index or the Insights API.
  • Tasks define when and how a sync runs, for example, on a regular schedule.
  • Transformations change your source data before it reaches the destination. They’re optional, and you add them to a destination.

​
Authentication

Connectors authenticate with your sources and destinations. Each source supports different authentication methods, such as basic authentication or a Google service account. Algolia indices require an API key with the following ACL:
  • addObject
  • deleteIndex
  • editSettings
Manage your connector credentials in the Authentications tab of the Algolia dashboard.

​
Allow Algolia IP addresses

If you restrict access to your source, allow these Algolia IP addresses:
  • 104.196.103.173
  • 35.234.69.129

​
Task status and alerts

If a task fails more than five times in a row, Algolia deactivates it and sets its status to critical in the Connector Debugger. Algolia also sends an email to every address associated with your Algolia application.

​
See also

Last modified on August 24, 2026