> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/workflows/mock-data.md).

# Mock Data

For Code Runner and Formatter

Users can now manually override DataHub variables using mock JSON data, directly from the DataHub. This ability allows configuring and testing step responses even before a workflow is synced, specifically within Code Runner and Formatter steps.

#### How It Works

* Locate a Code Runner or Formatter step in the DataHub.
* Click the mock data icon next to the step response.
* A popup will appear allowing you to edit and input mock JSON data.
* The provided mock data will:
  * override the existing response for that step.
  * be used as the response for downstream mapping or logic.
  * be replaced automatically when the workflow is synced and a realtime response is generated.

#### Use Case

This is particularly useful for:

* Testing workflows before real data is available
* Manually configuring mappings when building new flows
* Debugging formatters or custom logic using controlled input

#### Example

Mock JSON data:

```json
{
  "orderId": "12345",
  "status": "PENDING",
  "customer": {
    "id": "9876",
    "email": "test@example.com"
  }
}
```

This input will be treated as the step response for downstream mapping or transformation logic.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfXHKmMVSJdCL6eI0hGiNbrUJp2q25DQKXAbj-udYCt8bMbgd4YPjsVMDmf_mur6U0CGzxSUwrZLigOMqlKtjj87n2Oa9gFAqN8Hpi9PWD5JtbvZptC4fGxHL-Xg3Q9CR3MLJ3oSQ?key=wC4f4SBvUvQBDAaSHX4Z5qRA" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcT79yOnvawF1vnumCXadVHaPCbSWoCGXXsAZIyMW31VsMrTZqOQ5L9caRlYnjUuWJgGNzx3zKBxgeN4Gc4GY3fRp_iBvvKgtGxtM2wFzLmK9nvU68K5vZU6uSKKsXDjmwkcd_aBA?key=wC4f4SBvUvQBDAaSHX4Z5qRA" alt=""><figcaption></figcaption></figure>

<br>


---

# 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.dckapintegrator.com/project-manager/workflows/mock-data.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.