Connectors

Attach references in the landing-page or studio composer. The local workspace stores attachments in your browser; cloud projects keep private originals behind your own account. Exporting the supported concept formats is available on every plan.

Reach your projects from a script, a build pipeline or an AI assistant such as Claude. A token acts as you, carries only the permissions you choose and its own run budget, and can be revoked at any time. The developer documentation has the full instructions.

Revision shares and workspace changes post into a channel in your own Slack workspace or Teams tenant. Messages carry the event and a link, never a brief, a document or an email address, and anyone following the link still signs in and passes the same permission checks. Your company administrators add the channel, and Nordform enables the connection per company.

Send a design and an offer to a customer as a branded page opened from a link: no account on their side, the documents you granted and nothing else, every download logged, and an answer recorded against the exact revision. Payment and approval happen outside the page. The page is also the customer's order view: the revisions you have sent them and what changed between them, each file with its hash, the evidence behind the revision and its limits, and their change requests in their own words, which you answer by naming a revision. From the page they can mint a connection token so their own tools read the order over MCP; see the API guide.

The discussion threads on a revision leave as a BCF 2.1 archive, one topic per thread with its comments and a viewpoint, carrying the same element identifiers as the IFC export. For a design saved to the cloud, the findings from its invited reviewers go in the same archive, each labelled with the revision it was written on, the reviewer’s name, its open or resolved state and the view the reviewer saved. An archive written by another tool is read back onto the current revision, and anything it cannot place is listed by name; a reviewer’s finding coming back is not written into the review. The test suite checks the exported files against buildingSMART’s published BCF 2.1 schemas.

Give a design an address and post to it from anywhere: a Slack app, a mail forwarder, a Teams or Zapier flow, a script. The hub also has a mail address of its own, shown once when it is opened, so a fabricator or a customer can simply reply to a message and the reply lands on the design. Files attached to the mail are kept beside it for you to open; the hub reads only the text. What arrives is kept on the design and read; a change request can be run as a proposal, which a person adopts like any other. Comments and change requests from the design's own reviews, comments on the blocks its delivery document draws from a version, and notes brought back from a BCF file arrive there too, unless you switch that off; the people writing them are told so above the box. Webhooks tell your tools when a message arrived, a run's scenarios are ready or a run failed, and when a package is issued, a sign-off given, a decision recorded or a version adopted in the workspace. Connect Slack connects a channel through the Nordform Slack app once that app is configured, and the design answers where a message came from, in its Slack thread or by mail to a sender the owner approved, linking a read-only page; adoption happens in the workspace, and a company project answers in its own Slack channel. Connect explains it end to end, the API reference has the addresses and examples, and the demo tells one message’s story on a cooling plant.

Your own endpoint receives project events with a signature, an idempotency key and ordered retries. Company destinations are challenged before anything is sent, secrets rotate, and failed deliveries can be replayed.

A purchasing or ERP system can keep part data current on the components in a company's Standards library: article number, GTIN, supplier reference, unit price, lead time, availability and a few more, each with its unit, through the API or MCP. Each write is kept with its source and time, a retry with the same key is safe, and a part.updated company webhook says which component changed. Part data never changes a component's definition or an audit, and a price is recorded, not quoted.

In a personal project, open Meetings to connect Circleback, Granola, Fathom or Fireflies with your provider API key and a meeting-title filter. Matching notes import automatically. Summaries identify decisions, questions and actions with quotes from the original minutes; actions appear in your in-app notifications for review. Select source lines to request a revision. Provider API access is required; manual paste and normalized API imports are also supported.

Assistants can preview and explicitly adopt changes to timber kit designs, steel portal frames and pipe runs, sync registered family projects, prepare revision deliveries and manage reviews, private documents and permitted team operations. Whoever has the project open in Nordform sees the assistant there, marked as an agent, and is told when a new version is its save. Chunked file transfers support the existing 20 MB file limit. Native connection records track handoffs and adapter-reported read-back evidence; application-specific CAD editing goes through a native adapter.

In Settings, then GitHub backup, connect a repository you own and every project you save is copied into it as the same file a downloaded project backup is, so it opens again in Nordform. Attached images and original files stay in Nordform and are referred to by id; text read from attached spreadsheets and PDFs is part of the project, so it travels inside the project file. Restore brings back a project that is missing and never overwrites one that is still there. Access is a GitHub App installation you create and can revoke. A company can also mirror a house design's saved versions to its own repository and read a pull request there as a change proposal.