> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-nodes/call-node.md). # Call Node ## Description A call node is a system-facing step that allows you to connect logicnets together. ## Use By creating logicnets that focus on a particular function or series of actions you enable your logicnet designs to be more modular and reusable. You can connect your logicnets together using a *call node*. When someone is running through your application and reaches a call node the system "jumps" to the connected logicnet. The system either returns to the original logicnet after reaching the end of the connected one or moves to another connected logicnet, depending on how the nodes are connected. ## Editor Fields | Field Name | Description/Use | Type/Options | Optional/Mandatory | | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ | | Library project | When another project is configured as a library, it is selectable here and that enables public logicnets in that library project to be selected (using the ellipsis) in the Logicnet to call field. For more information on library projects, go to the support article called Libraries. | Text | Optional | | Logicnet to call | This is the name of the logicnet that will be called at this step in the overall pathway. | Text | Mandatory | | Context path | Putting a "container" name here will mean all variables created within the called logicnet will be stored in the context within this container, and NOT in the global context. | Text | Optional | | Collection | Repeating forms use this field to name the array in which all the form data is stored. Go to the Tab Control support article for more information. | Collection | Optional | | Class | This field can be used to access style settings to be applied to any UI within the called logicnet. It is also used automatically by the repeating form functionality. | Text | Optional | ### Visual Example ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-d2b52b90ea41b424de7559c8f9bffc95eddc315d%2Fe2d8699a-f2ce-4105-b107-b0fbe12eb521.png?alt=media) ## Advanced Use Call nodes play an important part in four substantial areas of functionality used in many LogicNets applications. Separate support articles have been written for these topics. * Many UI-heavy applications have some need for repeated input -- forms that collect the same types of data for different objects (e.g. locations, products) Download and import the project [ASF How-To Guide - Repeating Inputs](/release-9/example-gallery/how-to-guides/how-to-guide-repeating-inputs.md) for more information on this. * Libraries can house common logicnets for use across multiple applications. See [Libraries](/release-9/platform-documentation/publishing/libraries.md) for more information. * Functions are logicnets that take input parameters, go through a user-defined process, and issue output variables. The system calls them with a Call Node that shows an additional *Parameters* tab where you can enter the specific values to be used in the function. See [Functions](/release-9/platform-documentation/other-help-articles/functions.md) for more information. * Collapsible sections can be used to hide or show sections of information to the user, and make best use of the available space on screen. See [Collapsible Sections](/release-9/platform-documentation/process-nodes/collapsible-section.md) and check out the [example project](/release-9/example-gallery/example-projects-for-parts/collapsible-section-example-project-before-v7-4.md). --- # 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://community-test.logicnets.com/release-9/platform-documentation/process-nodes/call-node.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.