Guides
FuseBase Work
Browse every guide in this topic.
- Firecrawl Service in Fusebase Work: Quick Guide
- n8n Service in Fusebase Work: Quick Guide
- Calling Fusebase Work Agents from External Apps: Quick Guide
- Using Fusebase Apps as Connectors in Fusebase Work: Quick Guide
- Services in Fusebase Work: Quick Guide
- Agents in FuseBase Work
- How to connect Asana to FuseBase Work (example of a third-party MCP integration)
- Integration of agents/adapters with other services via MCP
- FuseBase Work – AI control center for the organization
Frequently asked questions
What is FuseBase Work?
FuseBase Work is where an organization sets up its AI coworkers. You create one for a company role, assign responsibilities and instructions, and connect the tools that role needs. People decide its access, what it may do, and what must be reviewed. FuseBase Work is powered by Paperclip.
How is an AI coworker different from a chatbot?
A chatbot responds to prompts. An AI coworker has a defined company role, recurring responsibilities, and the information and tools needed for that role. Its connected tools and narrower remit make its work more focused than a general-purpose chat window.
What are services in FuseBase Work?
Services are external capabilities you connect so an agent can do more than chat. The guides cover Firecrawl for reading web pages and n8n for running automation workflows, among others. Once connected, a service can be used by agents you have given permission.
Can FuseBase Work connect to the systems we already run on?
Yes, through MCP, an open standard for connecting AI to external systems. Asana is one documented example, and the same approach applies to other services that support it. Apps built in FuseBase can act as connectors too, giving an agent access to your own internal tools.
Can another system start a FuseBase Work agent?
Yes. External apps can call FuseBase Work agents, so an agent can run as one step in a process that starts elsewhere, including with a client request. You still define the role, permissions, and review requirements.
Is implementation help included?
Implementation, custom development, training, and ongoing support are scoped services rather than automatic parts of every subscription. Their scope is agreed with you before work starts.
Do we need an AI strategy before we start?
No. Begin with work you already do and an improvement you want, not a strategy document. Choose one repeatable process, put it on the platform, and add delegation where it is useful.
What does an AI coworker do here?
You give an AI coworker a company role rather than a one-off prompt, with responsibilities, the information it needs, and rules for its work. Your team decides what it may access, what it can do on its own, and what waits for a person.
Do we have to keep the portal in sync by hand?
Not when the same record is shared into a portal. Your team can update it internally and the client sees the current version, without maintaining a second copy or sending another attachment.