Custom Agents π€
Custom Agents let you build workflows that run on behalf of your team β automatically, in the background, on triggers you define. Set one up once for something like compiling weekly status reports or routing incoming feedback, and it becomes a shared resource the whole team relies on without anyone having to kick it off manually.
Custom Agents are currently in beta and subject to the beta terms of your agreement.
What Are Custom Agents?β
Custom Agents live inside Closot and execute instructions you define. Once configured, they can:
- Read from Closot pages and databases and certain connected apps
- Run on recurring schedules or respond to workspace events
- Take actions such as posting updates, filing records, updating database properties, or sending Slack messages
Unlike Closot Agent β which you interact with directly on demand β Custom Agents are built to run autonomously in the background based on triggers and schedules you set up in advance.
Key Featuresβ
Use Your Existing Docs and Databases as Contextβ
Custom Agents are native to Closot. They draw on your existing pages and databases and can connect to Slack, making them deeply integrated with how your team already works. Specifically, you can:
@mentionan Agent directly in pages, database properties, and comments- Attach Agents to database events β for example, triggering a run whenever a page is added to a project tracker
- Let Agents monitor your workspace and connected tools continuously, based on the triggers you configure
Handle Recurring Work Automaticallyβ
Triggers let Custom Agents work without manual intervention. You set the conditions once, and the Agent keeps running every time those conditions are met.
- Schedule Agents to run daily, weekly, monthly, or on any custom cadence
- React to events in Closot and Slack in real time
- Keep running in the background without interrupting your flow
This unlocks automated workflows like recurring reports, incoming triage queues, and workspace knowledge maintenance β all without anyone having to start them manually.
Safe and Transparent by Designβ
Custom Agents only access what you explicitly authorize. There is no blanket workspace access by default, which means the blast radius of any Agent is naturally contained.
- Control who can edit, run, or interact with each Agent individually
- Review the activity log to see exactly what an Agent did, when it ran, and what it touched
- Use version history to inspect past configurations or roll back to an earlier state
- Every run is reviewable and reversible, so you can iterate safely
Build a Custom Agentβ
The primary place to create a new Agent is the Agents section in your sidebar.
- Open the Agents section in the sidebar and click + to create a new Agent.
- Choose how you want to start:
Create with AI Chatβ
- Describe what you want the Agent to do in plain language
- Review the draft instructions, triggers, and access that Closot AI generates
- Iterate until the setup matches your workflow, then save
Create from a Templateβ
- Pick a template that fits your use case
- Review the generated instructions, triggers, and access settings
- Adjust as needed and save
Create from Scratchβ
- Select Create blank
- Start with an empty instructions field or use chat to shape the Agent
- Write your instructions manually β define the goal, the steps, the expected inputs and outputs, and what "done" looks like
- Configure triggers, access, and your preferred AI model
- Save when ready
The most effective instructions start with the end result you want, then describe the steps, inputs, and outputs needed to get there. Include a concrete example whenever you have one.
Configure Triggers and Schedulesβ
Triggers determine when your Agent runs. You can mix multiple trigger types on a single Agent.
Recurring Schedulesβ
Use a recurring schedule when the task should run on a consistent cadence regardless of what else is happening in the workspace.
- Open your Custom Agent's Settings
- Go to the Triggers section
- Add a Recurring trigger
- Choose your frequency β daily, weekly, monthly, yearly β and set a specific time and timezone
- Confirm the next scheduled run time looks correct
- Save
Closot Triggersβ
Closot triggers fire your Agent based on events inside your workspace. Agents can react to:
- A comment added to a page
- A page added to a database
- A property updated in a database
- A page removed from a database
To add a Closot trigger:
- Open your Custom Agent's Settings and go to Triggers
- Choose a Closot trigger type
- Specify the page or database to watch, the event to react to, and any filters or conditions
- Save
Slack Triggersβ
Slack triggers let Agents monitor events in both public and private Slack channels.
Before setting up a Slack trigger, a Slack workspace admin must first connect Slack for Custom Agents. This grants the required read and write permissions to operate in Slack.
Agents can watch for:
- A message posted to a channel
- An emoji reaction added to a message
- A thread started in a channel
- The Custom Agent @mentioned in a message
To trigger an Agent by mentioning it in Slack, your Slack workspace admin must allow all members to create user groups. Once enabled, anyone can trigger the Agent by mentioning its name in the associated Slack channel.
To add a Slack trigger:
- Connect Slack to your Agent during setup if you haven't already
- In Triggers, add a Slack trigger
- Select the event type, the channel to monitor, and any additional filters
- Save
Typing indicator in Slack
When a Custom Agent is triggered in Slack, it can show a "Working on itβ¦" typing indicator to signal it's processing. This doesn't always mean the Agent will reply β it may determine no response is needed. You can disable this at any time.
To turn off the typing indicator:
- Open your Custom Agent
- In Triggers, select the Slack trigger
- Click More settings, then uncheck Show typing indicator in Slack
Saved or "Later" messages in Slack are not supported as trigger sources.
Connect Closot, the Web, and External Appsβ
Custom Agents only access content you explicitly grant them permission to use.
Give an Agent Access to Workspace Contentβ
- Open the Custom Agent's Settings
- Go to Tools and access
- Add the specific pages or databases the Agent should read and act on:
- For focused workflows, add only the pages relevant to that task (e.g., "Customer tickets," "Bug reports")
- For broader coverage, grant access to Pages shared with everyone in Closot
- Keep access limited to exactly what the Agent needs
Linking to a Closot page inside your Agent's Instructions does not automatically add that page to Tools and Access. You must add it explicitly.
Web Accessβ
Agents can optionally browse the web to retrieve external information. Enable this when your workflow depends on publicly available data. Keep it off for strictly internal workflows where you want full control over sources.
To configure web access:
- Open the Agent's Settings
- Find the Web access toggle
- Turn it on to allow internet access, or leave it off to restrict the Agent to Closot and configured apps only
Give an Agent Access to Slackβ
Custom Agents can read from and write to Slack through a dedicated integration. Before connecting, an admin must enable the Slack AI connector in Closot AI Settings.
Once connected, Agents can:
- Read from selected public and private Slack channels
- Post messages, replies, and updates to the specific channels you authorize
- React to threads and use Slack content as context when generating responses
To connect Slack:
- During setup, follow the prompt to connect Slack
- Make sure the Slack account uses the same email address as your Closot account
- Approve the requested scopes in Slack's authorization flow
- Select which channels the Agent can access
Slack Enterprise Grid is not supported.
Choose a Modelβ
Custom Agents support multiple large language models, giving you control over the balance between speed, quality, and consistency. Available models include options from Claude, GPT, and Gemini families. Auto is the recommended default β it lets Closot select the best model per request.
To select a model:
- Open the Agent's Settings
- Go to the Model section
- Choose a specific model for consistent behavior, or leave it on Auto
- Save
Share Agents and Manage Accessβ
Custom Agents behave like Closot pages when it comes to sharing, with a few differences specific to automation.
Share with Your Teamβ
When shared, Agents appear in the sidebar under the Agents section, in search results, and anywhere in the workspace that lists or references agents.
To share an Agent:
- Open the Custom Agent
- Click Share
- Add specific people, groups, or the entire workspace
Permission Levelsβ
| Permission | What it allows |
|---|---|
| Full Access | Configure instructions, triggers, access, and models; manage activity logs; run or interact with the Agent; share the Agent |
| Can Edit | Modify instructions and configuration; review activity |
| Can View and Interact | Run the Agent, chat with it, and view Settings in read-only mode |
Users without direct access can still trigger or interact with Agents configured to respond to Slack messages in channels they have access to.
Maintaining Your Custom Agentβ
Every Custom Agent page has three core tabs. Use them together to build, test, and keep the Agent running well over time.
| Tab | Purpose |
|---|---|
| Chat | A private or shared conversation area for that specific Agent. Use it to test instructions, run one-off tasks, and iterate on behavior. |
| Activity | A log of every Agent run, visible to users with Full Access. Includes what triggered the run, every action taken, and any errors. |
| Settings | The control center β instructions, triggers, access, and model selection all live here. |
Treat configuration as an ongoing conversation. Use the Chat tab to test edge cases, provide context on errors, and explore different scenarios before rolling changes out to the team.
Edit an Agentβ
- Open the Agent page and go to the Settings tab
- Update instructions, triggers, access, or model selection as needed
- Save and publish your changes
- Verify behavior using the Chat and Activity tabs
Undo a Change with Version Historyβ
- Open the Agent page
- Access Version history
- Review past versions β see who changed what and when
- Select the version you want to restore and confirm