> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/user-guide/action-widget.md).
# Action widget
You do not need to go to Newsroom Planner to create a full package with article, plan and assignment. You can do so wherever you are by the Action widget up to the right.
You have a possibility to create an article with a plan and an assignment even if you are not in Newsroom Planner. For example, you work in Publication Planner and you need to create an article, a plan and an assignment but you do not want to open Newsroom Planner because you do not want to leave Publication Planner right now. Then you can open the action widget in the top bar and create the full package.
It is possible that your modal has different components compared to what you see below, it is your organization that decides which components you have in this dialog.
If you choose Create, the article, plan and assignment is created in the background and you can continue working in the workspace you are in.
If you choose Create and open article, the article will be opened in a modal and the plan and assignment is created in the background.
---
# 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.navigaglobal.com/newsroom-planner/user-guide/action-widget.md?ask=&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.
