Ready-made solution

When to use it

Choose Ready-made solution when a user needs to install a prebuilt working scenario into a project: agents, segments, landings, and other related resources. This type suits a reusable funnel or industry template rather than connecting an external API through OAuth.

How the solution enters a project

The user opens the ready-made solution in its separate catalog and installs the latest published version. Senler creates copies of the resources in the target project, connects them according to the version, and then shows the initial setup steps prepared by the developer.

A ready-made solution is not installed as a plugin and has no application OAuth settings. Use Website integration for an external service and Plugin for agent actions, automation steps, or an embedded user interface.

What the developer should configure

1. Create a Ready-made solution application. Open Ready-made solution in its menu and create the source project.
2. Assemble a solution version draft and add the required resources.
3. Add installation steps that the user completes when installing the solution for the first time. Check the resources and steps, then publish the version.
4. For later releases, add update steps when existing installations require user action.
5. Complete the application card, add documentation, and meet the catalog publication requirements.

New installations receive the latest published version. An existing installation can be upgraded to it: automatic versions apply in the background, while an After Confirmation version is started by the user and may contain separate update steps.

Access to dialogs and agent settings

• The switch that grants the developer access to related dialogs appears automatically during installation and is enabled by default. The owner of the installing project can turn it off before installation or later in application management.
• The developer cannot require or independently enable this access in another user's project. When access is enabled, the developer sees only dialogs where ready-made solution agents participated; other dialogs and project entities remain unavailable.
• Show agent settings in projects determines whether the user can open the instructions, model, MCP, Knowledge Base, variables, and other settings of installed agents.
• When settings are hidden, the agent remains available for testing in the project.

Source project

A ready-made solution is assembled from resources in a separate developer source project. There you can configure agents, segments, landings, and triggers, connect test channels, and verify the scenario itself before creating a release.

When a version is published, Senler stores separate snapshots of the selected resources and their dependencies. Later source-project changes therefore do not alter the published version or resources already installed from it. A ready-made solution cannot be installed into its own source project.