> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/build-and-improve/tutorials.md). # Tutorials Step-by-step guides for the most common things you'll do in Lleverage. While video tutorials are being prepared, these pages walk you through the same ground. ### Start here * [**The Agent**](/run-operations/agent/getting-started.md) - meet Llev, your AI coworker, and run your first task in chat * [**Workflow Copilot**](/build-and-improve/automate/build-a-workflow/workflow-copilot.md) - describe a process in plain language and let the Copilot build the workflow for you (temporarily unavailable while it is being improved) ### Build a workflow * [**Triggers**](/build-and-improve/automate/build-a-workflow/triggers.md) - choose how your workflow starts: a form, a chat, an API call, a schedule, or an integration event * [**Action Cards**](/build-and-improve/automate/build-a-workflow/canvas-reference/action-cards.md) - add and configure the steps that do the work * [**Variables and Data Flow**](/build-and-improve/automate/build-a-workflow/variables-and-data-flow.md) - pass data from one step to the next * [**Run Panel**](/build-and-improve/automate/test-and-publish/run-panel.md) - test your workflow with sample inputs before it goes live ### Go live * [**Publishing Workflows**](/build-and-improve/automate/test-and-publish/publishing-workflows.md) - share your workflow as an app, API endpoint, or schedule * [**Activity Monitoring**](/build-and-improve/monitoring.md) - follow runs and dig into what happened --- # 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.lleverage.ai/build-and-improve/tutorials.md?ask=&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.