Applications

Application list

In the developer section, Applications opens your application list. Here you can find an existing application or create a new one; after opening an application, the cabinet shows only the sections supported by its type.

When at least one application exists, this section displays a table with its name, type, creation date, publication status, and webhook statistics. The Accepted for delivery and Errors columns use the selected 7-, 30-, or 90-day period. Applications with more accepted operations in that period appear first; ties are ordered with newer applications first.

On a narrow screen, the date and webhook statistics are hidden, and an ordinary status may appear as an icon only; its full name remains available in the tooltip. Pending moderation stays visible at every width.

The Search applications... field searches the name, description, website address, type, and publication status. Clear or refine the query when there are no matches.

Select an application row to open its settings. The Publication column shows whether the application is private, pending moderation, public, or rejected. For Pending moderation, select the badge to open the explanation and submission date; the status updates automatically after review.

The actions menu lets you open the application. Open website appears only when a website URL is saved in the application settings.

How to create an app

Open the developer app list.

1. Select Create app to open the new application form.
2. Enter a name, then complete the description: on the Russian tab, add Russian text; on the English tab, add English text when needed.
3. Select the app type. It cannot be changed after creation.
4. Select Create.

For a Website integration, project and user scenarios are configured independently after creation under OAuth. One application can use both scenarios.

Choosing a type

• Website integration is for an external service with its own website and server. The user connects a project through OAuth, and the service works with permitted data through the Senler AI API.
• Plugin adds HTTP or MCP actions to agents, automation steps, MCP application actions, and, when needed, an embedded interface. A plugin can provide one or several of these capabilities.
• Ready-made solution installs a prebuilt set of agents and other resources. It suits a reusable workflow, template, or funnel.

Open the child page for the required type to see its capabilities, constraints, connection flow, and pre-publication checks.

Application sections

• Settings, Installations, Members, Documentation, and Webhooks are available for every application type. Installations shows projects, connection trends, and a webhook delivery summary.
• OAuth and Agent events are available for Website integration and Plugin applications.
• Agent tools, Automation steps, Application actions, and the Embedded page are available only for the Plugin type. Application action settings are located inside the Embedded page section.
• Versions, installation steps, and update steps are available only for the Ready-made solution type.
• The purpose and connection flow of a Website integration are described on its type page.

Typical workflow

1. Define the user outcome and choose one of the three types.
2. Create the application and complete its shared details in both languages.
3. Configure the selected type's capabilities and test them in a test project.
4. Add user documentation and a working developer website.
5. Submit the application for moderation and verify its card in the appropriate catalog after publication.