Solutions

Solutions are Fruxon-curated agent blueprints — pre-built flows for common use cases (customer support, travel planning, sales triage, RAG over docs, …) that you can clone into your tenant in a couple of clicks. A solution carries everything the agent needs except your credentials: the flow, sub-agents, integration configs (no API keys), knowledge-base shape, LLM config picks, and an opinionated set of tools.

You bring the credentials; the solution brings the structure.

Why use a solution

Building an agent from scratch is the right choice when the use case is novel or your domain is unusual. For the 80% of cases that look like "a thing teams build over and over", a solution gives you:

• A working flow on day one, not week one.
• Sensible defaults for tools, prompts, sub-agents, and step boundaries.
• A reference implementation you can fork freely — clones are independent of the source.
• A migration path from "Fruxon-managed pattern" to "tenant-owned agent" — the clone is yours to edit, version, deploy.

Browse the gallery

Open Solutions in the sidebar.

Each solution card shows:

• Display name and short description.
• Category (e.g. Travel, Support, Sales, HR, Research).
• Tags for finer filtering.
• Integrations used — the shape of the credentials you'll need to plug in after cloning.
• Preview — opens a read-only view of the flow, sub-agents, and tools.

Use the category filter and the search box to narrow down. Solutions are global (curated by Fruxon), so what you see is the same across organizations.

Clone a solution

1. Open the solution card and click Preview to inspect the flow.
2. Click Use this solution. Pick a name for your copy (defaults to the solution's display name; rename to your team's convention).
3. Fruxon clones the solution into your tenant as a new agent. The clone is:
   • A normal tenant agent — fully editable, versionable, deployable like any other.
   • Independent of the source — future updates to the solution don't flow into your clone, and your edits don't flow back.
4. You land in Agent Studio with the cloned agent open.

Bring your own credentials

Solutions include integration config shapes (which integration each step uses, sandbox routing, scopes) — but never the credentials themselves. The clone arrives with integration configs flagged "missing credentials". You fill them in:

1. In the agent's Integrations panel, open each flagged config.
2. Authenticate via the integration's normal flow (OAuth, API key, etc.).
3. Pick the OAuth scopes you want to grant where applicable — see each integration's guide for what each scope unlocks.

Once every required config is wired, the cloned agent can be tested and deployed.

What gets cloned

A clone carries the complete blueprint:

The clone is created at the draft revision stage. Saving it produces a normal revision; deploying makes the cloned agent reachable via the REST API and connectors.

Iterating after a clone

A cloned solution is a normal Fruxon agent — everything that applies to authored agents applies here too:

• Test from Studio. Use the canvas Test panel against representative inputs before deploying.
• Run an evaluation. Pair the clone with a small golden dataset and gate deploys on quality. See Evaluations.
• Add an Inline Judge. Wire Inline Judge on the customer-facing steps once you have a stable rubric.
• Trim what you don't need. Solutions are often built broad; remove the steps and tools you won't use to keep the agent fast and predictable.

Solutions vs. agents

If you find yourself repeatedly building the same agent shape across tenants or for different customers, treat it as a "solution-worth pattern" and capture the clone as your team's golden version. (Tenant-private solution authoring is on the roadmap.)

Next steps

• Creating Agents — full walkthrough of an authored agent (works the same after a clone)
• Agent Studio — the canvas you'll land in
• Integrations — wire up the credentials the clone needs
• LLM Providers — pick configs for each step
• Evaluations — gate deploys on quality