> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/start-here/run-your-first-workflow.md).

# Run your first workflow

Run a read-only health check, then a controlled draft, and learn how to check results.

Start with something that cannot change your site, then try a draft you review before publishing.

## 1. Read-only: Site health check

{% tabs %}
{% tab title="From Chat (Ask)" %}

1. Open **WP AI Manager > Playbooks** and find **Site health check** under Maintenance.
2. Select **Ask**. Chat opens with the playbook instructions.
3. Read the summary of performance, SEO and content gaps. Nothing is written.
   {% endtab %}

{% tab title="As a Task (Automate)" %}

1. On **Site health check**, select **Automate**. The Task review screen opens.
2. Check the inputs, then select **Run now**. Opening the link does not start a run.
3. Follow progress in **Run history**, then select **View result**.
4. Optional: **Manage schedule** to get a monthly briefing by email.
   {% endtab %}
   {% endtabs %}

## 2. A controlled draft: Write a blog post

1. In **Playbooks**, choose **Write a blog post** and select **Guided**.
2. Enter a topic and a short brief. Audience, tone, length and call to action come from Site Knowledge content defaults unless you change them.
3. Confirm. Chat shows a **Content brief** card. Use **Regenerate** if it misses, then **Write the draft**.
4. The draft is saved as a **private draft post**. Open its preview or edit link from the result card.
5. If an SEO plugin is active, review the suggested title and description and choose **Save to the page**.
6. Publish from WordPress when you are happy.

{% hint style="info" %}
A milestone only counts when a tool succeeded. If the assistant says "I created the post" but there is no result card with a link, nothing was saved.
{% endhint %}

## 3. Check what happened

* **Result cards** in Chat show what ran, with preview links and an **Undo** button where supported.
* **Home > Recent changes** lists the newest five changes in words, with where they came from (**via Chat** or **via Task**).
* **History** lists every recorded change, filterable by domain.

## The workspace at a glance

The top bar has seven destinations: **Home**, **AI Chat**, **Playbooks**, **Site Knowledge**, **History**, **Integrations** and **Settings**. Tasks live under **Playbooks > Tasks and runs**. See [The workspace](/documentation/work-safely/the-workspace.md).

Before a broad change, read [Approvals, Undo and History](/documentation/work-safely/approvals-undo-and-history.md) and [Backups and restore](/documentation/reference-and-help/backups-and-restore.md).


---

# 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.3techagency.com/documentation/start-here/run-your-first-workflow.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.