> For the complete documentation index, see [llms.txt](https://dev.ubidots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ubidots.com/plugins/plugins-development.md).

# Plugins development

The development of a plugin, regardless of its type, involves creating the source and configuration files that define the plugin's identity and functionality. These files are then organized into the file structure defined by Ubidots, as described in the previous sections. The process is illustrated in the following flowchart:

<figure><img src="https://884329393-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhzNRg0B4ECiNXc093G%2Fuploads%2F8UhU9nKWrXwWsqJrrdr3%2Fimage.png?alt=media&amp;token=302fb2ed-a1ab-441b-aec0-d34ad4838d6a" alt="" width="375"><figcaption></figcaption></figure>

The process consists of the following steps:

1. Establish the plugin's file structure.
2. Add the appropriate content to the individual files that make up the plugin.
3. Define the plugin version in the manifest file.
4. Compress the files.

For detailed information about each plugin type, visit its dedicated page:

{% content-ref url="/pages/rOXxLSuVRECFLwBSShdE" %}
[Cron](/plugins/plugins-development/cron.md)
{% endcontent-ref %}

{% content-ref url="/pages/uMjYgcn6XkaTixPJ3k3G" %}
[Webhook](/plugins/plugins-development/webhook.md)
{% endcontent-ref %}

{% content-ref url="/pages/rS0xzSFJNeWovSJ42Sfh" %}
[Widget](/plugins/plugins-development/widget.md)
{% endcontent-ref %}

{% content-ref url="/pages/3swuePrz8tIrfNH4G7Er" %}
[Device](/plugins/plugins-development/device.md)
{% endcontent-ref %}


---

# 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://dev.ubidots.com/plugins/plugins-development.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.