Integration
Twin agents pull updated BIM model data from Speckle, generate change summaries, and push results to Notion or Google Docs—on a schedule or on demand.
Integration guide
Twin treats Speckle Systems as part of a larger workflow, not as an isolated connector. An agent can read the relevant records, combine them with context from other tools, decide what needs to happen next, and report the finished work back to the team.
The page below shows the practical automation patterns for Speckle Systems: what the agent can monitor, which actions it can take, and how the workflow stays observable when it runs on a schedule.
Common starting points include bim model change monitoring, model data export and sync, customer support with speckle systems. Each example is designed to become a reusable agent, so teams can start from a narrow job and expand it as the process matures.
Twin is most useful when manually transferring BIM data from Speckle into docs or project trackers creates stale records and dropped follow-ups. Twin runs the transfer on a schedule so the destination is always current without anyone touching it.
Real Speckle Systems workflows the Twin community runs every day, ready for you to clone.
Pull updated model data from a Speckle repository and detect what changed since the last run.
ExploreSummarize model diffs and write structured reports to Google Docs or Notion pages for the project team.
ExploreWatch incoming webhook events from Speckle and trigger downstream steps when a commit or schema update arrives.
ExploreWrite repository details, deployment states, or issue records from Speckle into Notion databases automatically.
ExploreThree steps from idea to a running Speckle Systems agent.
Connect via OAuth
Sign in to Speckle Systems once. Twin securely manages the connection and handles token refreshes for you.
Describe the workflow
Tell Twin in plain English what you want done in Speckle Systems. The agent figures out the API calls itself.
Twin builds and runs
Twin assembles the agent, runs it on demand or on a schedule, and adapts when Speckle Systems responds in unexpected ways.
What makes Twin a better fit than a generic automation tool.
Manually transferring BIM data from Speckle into docs or project trackers creates stale records and dropped follow-ups. Twin runs the transfer on a schedule so the destination is always current without anyone touching it.
Speckle workflows may require structured API calls or browser-level steps depending on what your connection exposes. Twin handles both and falls back to browser automation when the API doesn't cover a needed step.
A Twin agent watches Speckle Systems continuously and takes the next step the moment something changes — no polling dashboards, no scheduled cron in the middle of your morning.
Be the first to build a Speckle Systems agent.
The Twin community hasn't published a Speckle Systems agent yet — describe what you'd like to automate and we'll build it for you in minutes.
Build the first Speckle Systems agentPatterns that show up across the Twin community — start from one and adapt it.
Watch Speckle repositories for commits and surface diffs to your project team.
Export Speckle model metadata into structured sheets or databases on a schedule.
Combine Speckle Systems with the rest of your stack to run this workflow on a schedule.
These related integration pages give crawlers and readers another path through the automation catalog. They connect Speckle Systems to nearby apps, categories, and paired workflows that teams often evaluate together.
See all integrationsStart building with Twin. Cancel any time.
Stay in the loop
Get the latest product updates, tips, and insights delivered straight to your inbox.
No spam, unsubscribe anytime. We respect your privacy.