> For the complete documentation index, see [llms.txt](https://docs.openalgo.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openalgo.in/new-features/chartink-integration.md).

# Chartink Integration

OpenAlgo now supports seamless Chartink integration for automated trading based on scanner alerts. Key features include:

• Automated Order Placement: Place orders automatically based on BUY, SELL, SHORT, or COVER alerts.

**• Dual Queue System:**

**• Entry Orders**: Fast processing for BUY/SHORT (up to 10 orders per second).

• **Exit Orders**: Priority handling for SELL/COVER (1-second delay per order).

• **Custom Strategy Setup**: Configure symbols, quantities, and product types (Intraday/Positional).

**• Auto Square-off:** Automatically close intraday positions sequentially.

<br>

Simply connect your Chartink webhook, configure strategies in OpenAlgo, and automate your trading flow.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openalgo.in/new-features/chartink-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.