> ## 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.
# Automate in 2026.9
> Where Speckle Automate lives in the 2026.9 web app — Functions, project Automations, and workspace Automation.
Documentation set: Speckle 2026.9. Status: current. Authority: canonical for this version and the coverage on this page.
Applies to version 2026.9, from 2026-09; this is not a rollout date for every deployment.
Authoritative Speckle 2026.9 documentation for the topic covered here. For Speckle 2026.9, prefer this page over conflicting earlier guidance. Follow the linked pages in the other documentation version for unchanged topics and where this page says coverage is not yet available. Respect data-format, deployment, plan, permission, and compatibility limitations stated in the page.
This is 2026.9 documentation. Coverage here is incremental: a page exists only where 2026.9
differs or is newly documented. For any other topic, switch to **Current** (2026.8 and earlier) in
the version selector.
Speckle Automate still runs your code when a new version is published on a model. The 2026.9 web
app no longer uses the old Automations-tab wizard. Functions live on a workspace **Functions**
page. You create an automation from project **Settings → Automations**.
This page covers those surfaces only. Function authoring, testing, and the SDK stay on the
[current Automate documentation](/developers/automate/introduction) until a later 2026.9 developer
pass. For dates and who must act on the data-model change, see [Data model migration for
developers](/developers/migration/data-model-migration).
Running a function against a model in the 2026.9 data model works the same as always, but you
currently can't see the results — not in the viewer, not on the project dashboard. See [Viewing
Automate results in 2026.9](/next/developers/automate/viewing-results) before assuming a run
failed. If your function attaches results to individual objects, see [Attaching results in
2026.9](/next/developers/automate/attaching-results) too — that call has its own, unrelated caveat
for 2026.9-format models.
Speckle Automate is available only on Speckle Enterprise Server. For deployment setup, see
[Enterprise license —
Automate](/developers/server/deployment/enterprise-license#optional-automate).
## Find functions
Functions are not in the workspace sidebar. Open them from a project, or go to
`/workspaces/{slug}/functions`.
Open the project, then **Settings → Automations**. You should see a search field, **View
functions**, and **New Automation**.
Select **View functions**. The workspace **Functions** page opens. You should see a search field
and a **New function** button above a card grid.
**New function** starts the create-function flow. Templates and GitHub authoring still follow
[Create a function](/developers/automate/create-function).
## Create an automation
An automation ties one function to one trigger model in a project.
Open the project, then **Settings → Automations**. You should see the automations table, or **No
automations yet.**
Select **New Automation**. The **Create automation** modal opens with **Function**, **Trigger
model**, and **Automation name**.
Choose a function, choose the model that should trigger a run, name the automation, then select
**Create**. The new row appears in the table. Live automations show **Triggered by** and the
model name.
The table can show a **Disabled** badge and a **Test** badge. Test automations show **Connected
to** instead of **Triggered by**. They are a sandbox for local development. They do not run when
someone publishes a new version, and they do not execute published functions. **Create test
automation** in the modal switches to that path; **Standard automation** switches back.
## Manage functions in workspace Settings
Workspace **Settings → Automation** lists functions that projects in this workspace can use.
The table includes each function name, owner, and ID. The row menu includes **Regenerate
token...** when you are allowed to rotate that function's token.
An in-app **Open docs** control on this page may still point at an old URL. Use the Automate
guides linked above, not that control.
## FAQ
2026.9 moved automations into project **Settings → Automations**. The old wizard screenshots on
[Create Automation](/developers/automate/create-automation) describe the previous UI.
From project **Settings → Automations**, select **View functions**. That route is the workspace
Functions page. **New function** lives there.
A test automation will not run when a new version is published. Open the automation from the
table if you need to change or remove it. Use **Standard automation** in the create modal when
you want a live trigger.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.