Agent Platform
How the Flourish Agent Platform fits together: what an agent is, where you build one, and the ways people reach it.
Overview
The Flourish Agent Platform runs AI agents for your organization. An agent is an assistant you set up once and put to work wherever it is needed: answering questions on your website, helping your team with their work, or running quietly behind an automation.
Each agent carries its own:
- instructions: who it is and how it should behave;
- tools: what it can do, such as search the web, read your documents, work with your data, or write and run code;
- knowledge: the files, websites and datasets it draws on, and other agents it can ask for advice;
- memory: whether it remembers people between conversations, and whose memory it keeps;
- safety screening of what people send in and what it sends back;
- a monthly spending limit, if you give it one.
You change an agent through versions: work on a draft, try it, and deploy it when it is right. Everyone who talks to the agent gets the deployed version.
Greenhouse
You build agents and work with them in Greenhouse, Flourish's app for the Agent Platform, at greenhouse.toflourish.org. It works on a computer and as an app on your phone.
In Greenhouse you chat with every agent you can reach, start forums where several agents take up a question together, and build agents yourself or with the Architect, an agent that designs and builds them with you in a conversation. See Greenhouse and Building agents.
Switching Agent Platform on in the Flourish Dashboard gives your team Greenhouse, and the dashboard opens it signed in. See Solutions & Billing.
Where people reach an agent
An agent built once can be reached in several places at the same time. They are different front doors onto the same agent, with the same instructions, tools, knowledge and memory.
| Where | Who it is for | See |
|---|---|---|
| Greenhouse | You and your team, signed in. | Greenhouse |
| A chat window on your website, or a link | Anyone, without signing in. | Chat on your website |
| A web app | Anyone the agent serves through a page of its own, such as a form or a dashboard, rather than a chat. | Web apps |
| Your own code | Automations, scheduled jobs and other systems, with no chat at all. | Daemon |
| Salesforce | Your staff and Experience Cloud visitors, inside Salesforce. | In Salesforce |
Wherever a conversation happens, it counts against the agent's own spending limit.
In Salesforce
If your organization works in Salesforce, the Agent Platform's Salesforce package brings the same agents inside it:
- an Agent Builder tab for building and managing agents without leaving Salesforce;
- a Chatbot component that puts an agent's chat window on a Salesforce page;
- a Web App component for an agent's web app;
- a Flow action, Invoke Agent (Daemon), for calling an agent from a Flow.
They are the same agents and the same settings. An agent your organization owns appears in both, whichever one it was built in. The pages under In Salesforce cover only what is different there, starting with Setup, which an admin does once after installing the package.