> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/appcademy/appfarm-fundamentals/actions-and-logic-fundamentals/context-parameters.md). # Context Parameters Context Parameters is a concept of having parameters that are *not* defined in the App Data section. For instance, when iterating some Data Source, you may want to access to iteration number inside the For-each Action Node. There are 2 types of Context Parameters: Action Parameters and Iterator Parameters. ### Action Parameters Action Params are parameters that may be set up per Action. These Parameters may be used for the logic inside an Action, and you may send values into these Parameters when the Action is triggered (e.g. from Event Handlers in the User Interfaces). #### Video You may see a video on Action Parameters here. {% embed url="" %} A video on Action Parameters {% endembed %} #### Documentation You may read our documentation [here](/reference/actions/action-params.md). ### Iterator Parameters Iterator Params are built-in parameters available for expressing logic inside iterating construction - such as inside the For-each Action Node, or inside an iterating Container in your User Interfaces. For instance, you may set up a Visibility Condition inside an iterating Container to only display an UI Component in the first iteration (for the first row). #### Video You may see a video on Iterator Parameters here. {% embed url="" %} A video on Iterator Parameters {% endembed %} --- # 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.appfarm.io/appcademy/appfarm-fundamentals/actions-and-logic-fundamentals/context-parameters.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.