> For the complete documentation index, see [llms.txt](https://readme.dhee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.dhee.ai/getting-started/train-your-bot/configure-workflow/no-code-approach.md).

# No Code Approach

If you do not have a backend Rest API to support your operations, you can use a no-code/low-code approach to log the information collected from the User in a spreadsheet.

![No Code approach](/files/BJU7Y4kbRZ7UNWxkkt49)

All inputs collected using the spreadsheet can be accessed using the *Reports->Statitics->Output Spreadsheet*.

In order to store the collected slots into spreadsheet, add a SAVE\_2\_SHEET action to the workflow editor. The SAVE\_2\_SHEET action accepts a single parameter - whitespace-separated list of slots that needs to be saved in the spreadsheet

![Save slot informtion in spreadsheet](/files/MUCEsd0MtU0depJVL6Fe)

As seen in the image above, pass in the 3 different slots which are being used in the *applyLeave* intent.

The spreadsheet created can be accessed using the *Reports->Statitics->Output SpreadSheet*. 

![Result in spreadsheet](/files/GXwxT5eApdeGowckcR2H)


---

# 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://readme.dhee.ai/getting-started/train-your-bot/configure-workflow/no-code-approach.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.