> For the complete documentation index, see [llms.txt](https://docs.kognitos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kognitos.com/legacy/legacy-experience/writing-automations/calling-other-processes/invoke-a-subprocess.md).

# Invoke a Subprocess

### Overview

Invoking a subprocess is one of the three ways a parent process can call a subprocess in Kognitos. When a subprocess is **invoked** using the `invoke` keyword, the parent process does *not* manage its execution or output.

{% hint style="success" %}
This method is ideal when the parent process does not need to track the status or output of the subprocess and can continue execution immediately after invoking it.
{% endhint %}

## How Can I Invoke A Subprocess?

This section explains how to call a process within another process as a **subprocess** using the `invoke` keyword.

#### Syntax

```
invoke {subprocess name} with
      {inputs}
```

#### Input Parameters

1. `subprocess name`: The name of the subprocess.
2. `inputs`: Any data elements the subprocess needs to run.

#### Example

In this example, the subprocess `verify applicant qualifications` is called with `the resume` as input.

```
invoke verify applicant qualifications with
      the resume
```


---

# 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://docs.kognitos.com/legacy/legacy-experience/writing-automations/calling-other-processes/invoke-a-subprocess.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.