> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/overview/automation-concepts/definition-of-terms.md).

# Definition of Terms

<table><thead><tr><th width="232">Term</th><th>Decription</th></tr></thead><tbody><tr><td>Process Composer</td><td>It is an integral component within IT-Conductor that enables the automation capabilities of the platform. It provides the interface to design and develop automation workflows by leveraging a drag-and-drop functionality where users can define the sequence of actions, dependencies, and conditional logic, all within a visually intuitive environment.</td></tr><tr><td>Process Definition</td><td><p>It is a template used for orchestrating various activities. It acts as a workflow automation framework that can be manually triggered to run or scheduled to automatically execute at a desired date and time.</p><p>It is composed of one or more activities that are woven together to create an automated workflow.</p></td></tr><tr><td>Activity</td><td><p>It is a component of a process definition that contains the actual task or operation. It contains various types of scripts, such as SQL, shell, Terraform, or Ansible scripts, which are executed to perform certain actions or manipulate data.</p><p>Each activity can also contain subprocesses that are also composed of one or more activities.</p></td></tr><tr><td>Subprocess</td><td>It refers to a smaller process that is part of a larger process. Each subprocess is composed of one or more activities, which contribute to the completion of the main process definition.</td></tr></tbody></table>


---

# 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.itconductor.com/overview/automation-concepts/definition-of-terms.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.