> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/integrations/integrations-overview.md).

# Integrations Overview

Compare Coresignal integration options and connect company, employee, and job data to existing workflows.

Integrations are designed to fit seamlessly into your existing data infrastructure minimizing setup overhead and letting you start working with high-quality data as quickly as possible.

Whether you are using company, employee, or jobs data, enriching records via API, or building automated pipelines, Coresignal provides structured integration options that align with standard engineering workflows.

This page covers the available integration methods, their technical requirements, and guidance on choosing the right approach for your use case.

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><a href="/integrations/coresignal-mcp.md"><strong>Coresignal MCP</strong></a></td><td>Connect AI assistants to Coresignal data with MCP</td></tr><tr><td><a href="/integrations/n8n.md"><strong>n8n integration</strong></a></td><td>Find information about Coresignal node</td></tr><tr><td><a href="/integrations/zapier.md"><strong>Zapier integration</strong></a></td><td>Get started with Coresignal in Zapier</td></tr><tr><td><a href="/integrations/clay.md"><strong>Clay integration</strong></a></td><td>Access Coresignal data in Clay</td></tr><tr><td><a href="/integrations/databricks.md"><strong>Databricks</strong></a></td><td>Analyze Coresignal data in Databricks</td></tr><tr><td><a href="/integrations/google-cloud.md"><strong>Google Cloud</strong></a></td><td>Receive Coresignal datasets straight to Google Cloud Storage</td></tr><tr><td><a href="/integrations/amazon-s3.md"><strong>Amazon S3</strong></a></td><td>Obtain Coresignal datasets through Amazon S3</td></tr><tr><td><a href="/integrations/azure.md"><strong>Azure</strong></a></td><td>Get Coresignal data directly in Azure Blob Storage</td></tr><tr><td><a href="/integrations/snowflake.md"><strong>Snowflake</strong></a></td><td>Load Coresignal datasets from cloud storage into Snowflake</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/integrations/integrations-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.