{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What types of data sources can Forest connect to?","acceptedAnswer":{"@type":"Answer","text":"SQL databases (PostgreSQL, MySQL, MariaDB, SQL Server, Oracle), NoSQL (MongoDB, DynamoDB), warehouses (Snowflake, BigQuery, Redshift), REST and GraphQL APIs, and SaaS tools such as Intercom, Pylon, Zendesk, HubSpot and Stripe. See every integration in the ecosystem directory."}},{"@type":"Question","name":"Does Forest store or copy our data?","acceptedAnswer":{"@type":"Answer","text":"No. Forest queries your sources live and writes back directly. Your data stays in your systems."}},{"@type":"Question","name":"Can we perform CRUD across all sources?","acceptedAnswer":{"@type":"Answer","text":"Yes. Create, read, update, and delete are supported on every connected source that exposes write access."}},{"@type":"Question","name":"How does Forest handle multiple environments?","acceptedAnswer":{"@type":"Answer","text":"Each environment (dev, staging, production) connects to its own set of sources via the Forest back-end config. The same workflows can run against different data."}},{"@type":"Question","name":"What if a source isn't supported out of the box?","acceptedAnswer":{"@type":"Answer","text":"The Forest SDK lets you build a custom connector in your language of choice. Custom connectors run inside your Forest back-end like any other source."}},{"@type":"Question","name":"What is the Connector Directory?","acceptedAnswer":{"@type":"Answer","text":"The Connector Directory is a curated list of official MCP implementations from SaaS vendors. Editors can browse and request connectors directly from the workflow editor. Admins get pre-filled configurations in Project Settings and can activate any connector in one click. Available today: Intercom, Slack, Microsoft 365, Amplitude, HubSpot, Notion, Monday.com, Square, Stripe, Razorpay, Zendesk, Snowflake, Pappers, n8n, Zapier, Workato. The list grows as new official MCP servers are released."}},{"@type":"Question","name":"Can Forest act as an MCP client?","acceptedAnswer":{"@type":"Answer","text":"Yes. Forest connects to MCP servers, from the Connector Directory or your own, and your workflows call their tools through MCP tasks. Each task lists the tools it may use, so AI cannot reach the others."}},{"@type":"Question","name":"Datasource or MCP connector: which do I need?","acceptedAnswer":{"@type":"Answer","text":"A datasource lets your team browse and edit a tool's data in Forest, as collections. An MCP connector lets a workflow call the tool to act or fetch data. Many tools offer both."}},{"@type":"Question","name":"How do you ensure customer data never leaves our environment?","acceptedAnswer":{"@type":"Answer","text":"The Forest back-end runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record."}}]}