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

# What is DataPipeline?

DataPipeline is a **low-code solution** for scraping projects, which **automates** your data collection. You can avoid writing complex code, stop maintaining your own scraper and therefore **reduce engineering resources and costs**.

With DataPipeline it is possible to automate your scraping jobs, receive the data where you need it and scale up your projects.

All features at a glance:

* Run up to 100 000 URLs, keywords, ASINs or Walmart IDs at once.
* Upload all of the input in an input field, with CSV or with a webhook, for more flexibility & dynamic scraping.
* Get results in HTLM, structured JSON or CSV.
* Schedule when you project should run automatically.
* Get your results delivered directly to your webhook.
* Get updates on the status for your pojects & the success of your jobs directly to your email inbox.

<figure><img src="https://921583510-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXJv4kz1e8RdAq9HrFwyo%2Fuploads%2FDWQTDu0DLDCRmCbHQCwD%2Fimage.png?alt=media&amp;token=adaa8ee0-850b-4dd7-9660-4ec239aa5e2d" alt="" width="375"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scraperapi.com/data-pipeline/what-is-datapipeline.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 `automate deployments from our CI pipeline` 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.