ruLog in to Senler

Ready-made solution

What this type is for

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.

What the user receives

The user opens the ready-made solution in its separate catalog, selects a published version, and completes the installation steps prepared by the developer. Senler creates copies of the resources in the target project and connects them according to the solution version.

A ready-made solution is not installed as a plugin and has no application OAuth settings. Use Website integration for an external service and Tool for agent actions or an embedded page.

What the developer configures

  1. Create a Ready-made solution application and select its source project.
  2. Assemble a solution version draft, check its included resources, and publish the version.
  3. Add installation steps when the user must select a channel, enter variables, approve access, or configure created resources.
  4. Complete the application card, documentation, and publication requirements.

A newly published version applies only to new installations. An already installed resource set is not updated automatically and remains part of the user's project.

Developer access and agent settings

During installation, the project owner decides whether the developer may access dialogs associated with the solution's agents. Access is limited to those dialogs and can be disabled before installation or later; the developer cannot enable it independently in another user's project.

The agent settings visibility option determines whether the user can open their instructions, model, MCP, Knowledge Base, variables, and other settings. Even when settings are hidden, the agent remains available for testing in the project.

Before publication

Test the version in an empty project, including required step order, variable substitution, user permissions, agent settings visibility, and documentation. Submit the application card for moderation only after at least one working version has been published.