> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/workflow-guide/creating-a-workflow.md).
# Creating a Workflow
On the workflow page click the plus (+) sign in the lower right corner to open a new workflow page.
Create work flow page
Give the workflow a name on the top line. TDO will automatically version control the workflow, so you don't need to enter anything there.
For now we will skip the second and third panes in this window (Work Flow Parameters).
In the fourth pane, you can create individual activities in your workflow. You can run one or more activities in a workflow and can mix API and shell (batch) calls.
To add an activity, type a name for your activity in the 'Activity Name' space and then select the type of call (REST API Call or Shell Script). Click the plus sign to the right to add it to the Activities section at the bottom of the page.
Work Flow with defined activities
Once the activities are added, save the workflow by clicking the 'Save' button in the top pane.
{% hint style="info" %}
You should test your API calls in a separate program (ex: Postman, SoapUI, Bruno, Insomnia, etc) before setting them up in TDO. TDO is not designed as a API call development and testing program, but rather to bring workflow automation closer to the test data end user.
{% endhint %}
---
# 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.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/workflow-guide/creating-a-workflow.md?ask=&goal=
```
`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.