> ## Documentation Index > Fetch the complete documentation index at: https://docs.speckle.systems/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These docs contain multiple Speckle product experiences. For Speckle 2026.9, prefer /next/ pages for the topics and changes they cover. The navigation label Current does not override this version-specific precedence. > Coverage under /next/ is incremental. Use Current documentation for unchanged topics and when a /next/ page says coverage is unavailable or explicitly refers you to Current. Do not infer a feature was removed from a missing page. > Read the page-specific documentation status, applicability, affected guidance and replacement links in agent-only content. Impacted, changed and superseded apply only to the stated scope; they do not mean the entire feature is deprecated. Historical connector guides apply only to the legacy connector described. > Match guidance to the customer's deployment version, model data format and connector. Respect plan, permission and compatibility restrictions. If an unknown version or data format changes the answer, ask a focused clarification; do not infer deployment version from the date alone. # Powering Your Automation Workflows > Speckle Automate is a fully fledged CI/CD platform designed to run custom code on Speckle models whenever a new version is available. Documentation status: changed for the changes in Speckle 2026.9 (from 2026-09). Affected guidance: 2026.9 Functions and project Settings Automations replace the old tab wizard. For these changes, read [2026.9 guidance](/next/developers/automate/introduction). For Speckle 2026.9, prefer the linked guidance only for the affected topics. This page remains applicable to earlier experiences and unchanged guidance. Do not treat the whole page or feature as deprecated. Three diagrams. Continuous integration: a model change enters a loop of merge report, quality check, and version control, producing a shared model. Continuous delivery: a loop of requirement tests, version integration, publish model, and generate deliverables. Continuous communication: a model change branches through three API paths out to Slack, OpenAI, and Microsoft Teams. Speckle Automate is a CI/CD platform for model intelligence and data automation.\ It runs your code automatically whenever a new version of a Speckle model is published, enabling tasks such as validation, reporting, or data transformation to happen instantly. As a developer, you can [create Functions](/developers/automate/create-function) that define what runs,\ and package them as [Automations](/developers/automate/create-automation) for others in your workspace to use. **No Server Required**: Automate runs on Speckle's infrastructure, so you don't need to deploy or manage your own server. If you need to orchestrate automations on external servers or services, you can use [webhooks](/developers/api/webhooks) to trigger workflows on your own infrastructure. ## Availability Speckle Automate is now available an Enterprise-only offering on [app.speckle.systems](https://app.speckle.systems).\ Enterprise plans include custom automation support by Speckle engineers. ## Capabilities * Run custom code automatically when a model updates * Generate reports or perform data checks without manual effort * Deploy reusable workflows across multiple projects * Integrate with GitHub or other version control systems * Review detailed logs and results directly within Speckle This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.