> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/campaigns.md).

# Campaigns

The home screen has the list of all your campaigns - Active, Paused, Draft and Archived. 

1. **Campaign ->** Each campaign has a set of sequences 
2. **Sequence ->** Each sequence has a set of emails 
3. **Email ->** The content can be either auto-generated by the content agent or written manually by a human.

<figure><img src="/files/j23tLR7DKw9tSTe5btyL" alt=""><figcaption><p>List of all existing campaigns</p></figcaption></figure>

Clicking on the edit icon allows you to edit all the properties of each campaign. You also have controls to delete, archive, activate and deactivate each campaign

{% hint style="info" %}
Clicking on the Analytics Icon provides you analytics for each campaign and sequence
{% 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://humanic.gitbook.io/humanic/campaigns.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.