# 9 Internal Workflows

There are no required internal workflows for candidate applications that implement the Workflow Building Block specification. Below is an example of how an internal workflow might run when responding to an API request.

## 9.1 Start a workflow process via API

To satisfy the initial 6.2 functional requirements a candidate application may implement the following internal workflow.

{% @mermaid/diagram content="sequenceDiagram
autonumber
participant E as External Application
participant W as Workflow Application
participant Q as Workflow Engine Queue
participant X as Workflow Engine Executor
E->>W: Call to start WF process with input data
W->>W: Create initial state for process instance with request body
W->>Q: Add process instance to queue
W->>E: Respond with 202 and process instance ID
X->>Q: Get process instance request from top of queue
X->>X: Execute workflow process instance
X->>W: Send results back to app" %}


---

# Agent Instructions: 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:

```
GET https://specs.govstack.global/workflow/9-workflows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.