How to use Osela, your AI assistant

Osela answers from your app’s context rather than giving generic recommendations. It uses your AI Profile, the plugins you already have installed, and the plugins available to your account.

How Osela works

Open Osela from the Marketplace and ask a question in your own words. Its answer streams in as it works through your request, and you can continue with follow-up questions in the same conversation.

Osela keeps the conversation context, so you can ask things like:

“Why did you recommend that one?”
“What would I need to set up first?”
“Would this work with the plugins I already have?”

Every conversation is saved, so you can return to it later.

Osela only recommends plugins that are real and available to your app. It does not invent plugins or recommend plugins you cannot add. If nothing in the Marketplace meets your needs, Osela can turn your description into a short build brief that you can take to Plugin Studio.

Osela provides recommendations and information; it does not change your app. It will not install, remove, or configure plugins for you. When you decide to use a plugin, you add it from the Marketplace yourself.

Requirements

Availability depends on your account configuration. If you do not see Ask Osela in the Marketplace, contact your account administrator.

Start a conversation

Log in and go to Builder.
Click + to open the Marketplace.
Click Ask Osela.
Choose one of the suggested starting points, or type your own question.

You can start with:

Compare two plugins for me — Compare two plugins side by side to help you decide which is the better fit.
I have a use case in mind — find me a plugin — Describe what you want to accomplish and Osela will find a suitable plugin.
Audit my setup — Review your setup for gaps, conflicts, prerequisites, and other issues.
What does this plugin do? — Understand what a plugin is designed to do, who it is for, and where it works best.

Read the answer as it streams in and ask follow-up questions in the same conversation.
When you find a plugin you want, add it from the Marketplace as you normally would.

What you can ask Osela

Find a plugin from a use case

Describe the outcome you want, rather than trying to guess a plugin name or category.

For example, instead of asking:

“Do you have a calendar plugin?”

try:

“I want members to book appointments with our staff.”

The second question gives Osela more context about what you are trying to accomplish, so it can match your need to what a plugin actually does.

Compare two plugins

When two plugins seem similar, ask Osela to compare them.

It looks at what each plugin is designed for and who it suits, helping you understand the meaningful differences rather than just comparing feature lists.

Understand a plugin

Before adding a plugin, ask what it does, who it is intended for, and where it works best. This can help you decide whether it fits your app and use case.

Check compatibility

Before adding a plugin, ask Osela whether it will work with your existing setup.

Osela can flag three types of relationships:

Conflicts — Two plugins should not be installed together, or overlap enough to create confusion for your members.
Prerequisites — A plugin depends on something that is not currently available in your setup.
Complements — Two plugins work particularly well together.

Check important compatibility warnings and prerequisites against the plugin’s own documentation before making a decision.

Audit your entire setup

Ask Osela to audit your setup when you want a broader review.

It looks for:

Capability gaps — Important capabilities your type of app may need but that your current setup does not cover.
Missing dependencies — Installed plugins that depend on something you do not have.
A clear core feature — Whether your app has a clear main capability at its centre.

An audit is particularly useful after you have changed what your app is for or added several plugins.

When nothing fits

If no Marketplace plugin meets your needs, tell Osela what you want to accomplish.

Osela can turn your description into a short build brief: a clear summary of what a plugin would need to do. You can then take that brief into Plugin Studio to build or customize a plugin instead of starting from scratch.

Tips for better answers

Keep questions focused.
One clear question at a time usually works better than a long message containing several unrelated requests.

Describe your members and their goals.
Give Osela context about who uses your app and what they are trying to accomplish. For example, “Our members are volunteers who sign up for shifts” is more useful than simply saying “we need scheduling.”

Use follow-up questions.
You do not need to restart the conversation to explore a recommendation. Ask why Osela chose a plugin, what you need to set up first, or how two options differ.

Check compatibility before installing.
It is easier to avoid a plugin conflict than to resolve one after installation.

Audit after significant changes.
Run an audit after adding several plugins or changing your app’s purpose. Those are good times to look for new gaps or dependencies.

Start a new conversation after changing your plugins.
Osela reads your installed plugins at the beginning of a conversation and keeps that picture throughout the conversation. If you add or remove a plugin while chatting, start a new conversation so Osela can work from the updated setup.

Ask about your goal, not the entire catalogue.
Osela is designed to find plugins that fit a particular need. It does not read every Marketplace entry for every question, so broad requests such as “show me every plugin that works offline” will not necessarily produce a complete catalogue-wide list. Describe what you are trying to accomplish instead.

Stay in the app you want to discuss.
Osela is scoped to the app you currently have open. Switch apps before starting a conversation if you want recommendations for a different app.

Troubleshooting

Osela says your app does not have an AI Profile

Set up an AI Profile for your app and continue in the same conversation. You do not need to start over.

Osela does not mention a plugin you expected

The plugin may not be available to your account. Osela only recommends plugins that you can actually add to your app.

Osela returns a short list

This does not necessarily mean there are no other plugins in the Marketplace. Ask about your specific use case instead. Osela is designed to recommend what fits your need rather than provide a complete catalogue search.

An answer stops partway through

Very long answers can be cut short. Ask a narrower follow-up question to continue.

Osela asks you to wait before sending another message

You may have sent several messages in quick succession. Wait a moment, then continue the conversation.

A long message is refused

Split the request into two or more shorter questions.

Osela does not seem to know about a plugin you just installed

Start a new conversation. Osela uses your installed-plugin context when a conversation begins.

About AI-generated answers

Osela’s answers are AI-generated. They are grounded in real plugin information and your app’s context, but they can still contain errors.

Osela describes what a plugin is designed to do; its answer is not a guarantee that the plugin will produce a particular result in your app.

Use Osela as a well-informed starting point, not as the final authority. For anything important—especially compatibility warnings and prerequisites—check the plugin’s own documentation before relying on the recommendation.