# Anatomy of a Plugin

### Overview

Omnata Plugins are built using Python, with the help of two Python packages. To build a plugin, you'll need to be familiar with Python, as well as understanding how API calls work.

The **omnata\_plugin\_runtime** package contains all the classes and decorators needed to construct a plugin class that the Omnata engine can communicate with.

The **omnata\_plugin\_devkit** package contains tools for developing, testing, and uploading plugins, but is not involved in any day-to-day sync activity.

Each Omnata plugin is packaged and distributed as a Snowflake Native Application. That means updates to each plugin occur independently of each other and the main Omnata Application. Plugin code is protected so that the Omnata Application, the customer, and other plugins cannot access it.

Here's how the Omnata App interacts with a plugin when configuring an outbound Sync:

<figure><img src="/files/MEI90poUmQf4eaeXGKSD" alt=""><figcaption></figcaption></figure>


---

# 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://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/plugins/anatomy-of-a-plugin.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.