Docs
Integrations and skills in Foundable
Integrations and skills help Foundable work with real context while keeping the product surface simple.
Updated · Published by Foundable
Overview
Useful tool access without protocol clutter.
Foundable uses native work surfaces, 150+ verified integrations, and specialized skills when the work needs them. Ted reads context and takes actions in the services a business already uses, and the operator should not need to understand protocol details to get useful work done.
Quick answers
Practical answers for the next decision.
How do Foundable integrations and skills work together?
Supported Foundable integrations give Ted available context and actions, while skills give Ted specialized ways to produce stronger research, pages, campaigns, documents, workflows, and operational outputs without exposing protocol details to the user.
How do Foundable integrations and skills work?
Foundable integrations and skills add supported context or specialized capabilities so the product can create better research, pages, campaigns, documents, workflows, and operational outputs without exposing protocol details to the user.
When should I connect an integration in Foundable?
Use a supported integration when Foundable needs live context, external output, or a repeat workflow for the job at hand. Start from the business outcome first, then connect only an available integration that helps produce it.
Connect only what helps
Use supported integrations when Foundable needs live context, external outputs, or a repeat workflow.
Keep permissions understandable
Operators should know which tools are connected and what kind of work they support.
Use skills for better outputs
Skills help Foundable produce stronger research, pages, campaigns, documents, and operational workflows.
What you leave with
What integrations make possible.
Workflow
How to use connected context.
Start from the job
Decide what Foundable needs to accomplish before connecting tools.
Install the right integration
Connect only the tool needed for the requested workflow.
Run a concrete task
Ask for an output that uses the connected context.
Review and adjust
Keep the workflow useful, permissioned, and easy to inspect.