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