> For the complete documentation index, see [llms.txt](https://docs.precisiontestautomation.in/scriptlessautomation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.precisiontestautomation.in/scriptlessautomation/welcome-to-scriptless-automation.md).

# Welcome to Scriptless Automation

Author: Prabhat Gaddam | Email: prabhat.gaddam\@precisiontestautomation.in | LinkedIn: https\://www\.linkedin.com/in/prabhat-g-9290ba89/ | GitHub: https\://github.com/PrecisionTestAutomation

## Overview

Scriptless automation is an innovative software solution designed to streamline your product's automation process in record time. As the name suggests, "scriptless" emphasizes the minimal coding required, making automation more accessible to those without extensive scripting expertise.

With our tool, users can effortlessly automate APIs and web services. While the current framework primarily supports API and Web automations due to their straightforward nature, we recognize the unique intricacies of mobile automation. We understand that mobile automation needs may vary among users, and we're dedicated to enhancing the framework accordingly. For specialized requirements in mobile automation, we encourage users to get in touch with us directly through our website. Our commitment is to provide an adaptive and user-friendly solution for all your automation needs.

## Discover More About Automation

{% content-ref url="/pages/eHfsoxfB0imV9FdegRj9" %}
[Automation platform intro](/scriptlessautomation/discover-more-about-automation/automation-platform-intro.md)
{% endcontent-ref %}

{% content-ref url="/pages/T1om9zAimnsASDZqEhGa" %}
[Advantages of Scriptless Automation](/scriptlessautomation/discover-more-about-automation/advantages-of-scriptless-automation.md)
{% endcontent-ref %}

{% content-ref url="/pages/nBuTC1qWBaEcIXrgN4HR" %}
[Release Notes](/scriptlessautomation/discover-more-about-automation/release-notes.md)
{% endcontent-ref %}

## Product Tools

{% content-ref url="/pages/EzMSZ6I4nrOZCBdAv2mB" %}
[Pre-request Tools](/scriptlessautomation/product-tools/pre-request-tools.md)
{% endcontent-ref %}

## Get Started

We've put together some helpful guides for you to get setup with our product quickly and easily.

{% content-ref url="/pages/iMQhuHuZe8r9YWR7e5QR" %}
[Start with Automation](/scriptlessautomation/get-started/start-with-automation.md)
{% endcontent-ref %}

{% content-ref url="/pages/Ir4FDeLE83BnxFWqMkVp" %}
[ScriptlessApi Automation](/scriptlessautomation/automation-platforms/scriptlessapi-automation.md)
{% endcontent-ref %}

{% content-ref url="/pages/GCYC0IGC6wmNQsJ8V9GK" %}
[ScriptlessWeb Automation](/scriptlessautomation/automation-platforms/scriptlessweb-automation.md)
{% endcontent-ref %}


---

# 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.precisiontestautomation.in/scriptlessautomation/welcome-to-scriptless-automation.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.