> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/admin/8.7/getprocessdata-workflow-application.md).

# GETPROCESSDATA Workflow Application

## Overview

The **GETPROCESSDATA** workflow application lets you retrieve process data values for a specified request. It is very useful for inter-process communications.

As an initial sub-process action, GETPROCESSDATA provides a flexible alternative to the sub-process parameters, since it involves no versioning management constraints with the parent process.

## Using default and other parameters

### Request

The required parameter request is `REQUEST_ID` (IN, numeric): the request ID that contains the process data to retrieve.

### Activity

The other parameters are defined in the workflow action according to your needs.

* **Parameter name**: The name of the remote process data to retrieve
* **Receive value into**: The process data to update

#### 📌 Example

To retrieve the value of the `COMPANY` process data into the `CUSTOMER_COMPANY` process data:

* **Parameter name**: `COMPANY` 
* **Receive value into**: `CUSTOMER_COMPANY`

The process data types must be the same. You can add an exception management to handle possible errors (e.g. invalid request ID).


---

# 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.workflowgen.com/admin/8.7/getprocessdata-workflow-application.md?ask=<question>&goal=<user_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.