> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/archived-merged-pages/transforming-data-with-pdi-archive/work-with-jobs/create-a-job.md).

# Create a job

Follow these instructions to create your job:

1. Perform one of the following actions:
   * Click **File** > **New** > **Job**.
   * Click the **New file** icon in the toolbar and select **Job**.
   * Hold down the CTRL ALT N keys.
2. Go to the **Design** tab. Expand the folders or use the **Entries** field to search for specific entries.
3. Either drag or double-click an entry to place it on the PDI client canvas.
4. Double-click the entry to open its properties window. For help on filling out the window, click the **Help** button that is available in each entry.
5. To add another entry, either drag or double-click the entry to place it on the PDI client canvas.
   * If you dragged the entry to the canvas, you can add a hop by pressing the SHIFT key and drawing a hop from one entry to the other.
   * If you double-click it, the entry appears on the canvas with a hop already connected to your previous entry.

When finished, save the job.


---

# 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.pentaho.com/pdia-data-integration/archived-merged-pages/transforming-data-with-pdi-archive/work-with-jobs/create-a-job.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.