Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 22, 03:15 UTC
docs: replace next steps with take it further in workplace-search
Match the background-agent cookbook pattern with concrete use case ideas and linked cards. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmitha Mallesh committed
Mar 11, 2026 at 02:38 UTC
2040e0e4016e5e6ff793315700a4c759df64d1f4
1 file changed
+11
-3
docs/content/cookbooks/workplace-search.mdx
+11
-3
@@ -115,7 +115,15 @@ into two phases. The team agreed in the thread.
115
3. The agent searches across apps, synthesizes results, and cites sources with links, channel names, or sender info.
116
4. The `USER_ID` in `.env` scopes all connections — swap it to switch users without changing code.
117
118
-## Next steps
118
+## Take it further
119
120
-- Restrict to read-only tools with `tags` when creating the session. See [Enable and disable toolkits](/docs/toolkits/enable-and-disable-toolkits).
121
-- Add more toolkits (Jira, Confluence, Linear) — no agent code changes needed.
120
+The prompt and toolkits are the only moving parts. Change them to change what the agent searches. Some ideas:
121
+
122
+- **Engineering on-call**: add PagerDuty and Datadog toolkits, ask "what incidents fired overnight and which PRs might be related?"
123
+- **Sales prep**: connect Salesforce and Gmail, ask "summarize all recent activity with Acme Corp before my call"
124
+- **Compliance audit**: add Jira and Confluence, ask "which security tickets are still open and do any docs reference the old auth flow?"
125
+
126
+<Cards>
127
+ <Card title="Background Agent" href="/cookbooks/background-agent" description="Run a similar multi-app agent on a cron schedule" />
128
+ <Card title="Enable and disable toolkits" href="/docs/toolkits/enable-and-disable-toolkits" description="Restrict tools to read-only with tags" />
129
+</Cards>