flo2

Set up Autodesk for cloud Revit

flo2's cloud-Revit helper runs real Revit in Autodesk's cloud (Autodesk Platform Services Design Automation) on a Revit file in your design, using your own Autodesk developer app. You set the app up once. Autodesk bills its use to you, by processing time.

It's optional: nothing else on flo2 needs an Autodesk account. Already set up? Your app's keys and your monthly limit are on your account page, under Cloud Revit.

A Create your Autodesk app

  1. Create an account. Go to aps.autodesk.com, click Sign in, then Create account, and follow the prompts. Keep the backup code Autodesk gives you somewhere safe.
  2. Get a plan. On the page that says you don't have a hub yet, click View options under Get an APS plan, or open Autodesk Platform Services and find its cloud APIs section. The free tier gives monthly access with usage caps on the paid APIs. Design Automation is a paid API, billed in Flex tokens per processing hour, so check that page for whether its cap covers what you need.
  3. Create a developer hub. Go to manage.autodesk.com, then Products and Services, then Hubs, and click Create hub. Choose APS developer hub, give it a name, and click Create and Activate.
  4. Register the app. On aps.autodesk.com, open your profile menu, choose My applications, pick your developer hub, and click Create application.
    • Name: any name you like.
    • Application Type: Server-to-Server App.
    • API Access: Automation API and Data Management API, nothing else.
    Then click Save changes.
  5. Copy the Client ID and Client Secret into a password manager.

    Never paste the secret into a chat, an email, or a file in a repository. flo2 asks for it in one place only, your account page (step 6), and never shows it again.

B Connect it to flo2

  1. Enter the keys on flo2.io. Open your account page, find Cloud Revit, and paste your Client ID and Client Secret. flo2 keeps them encrypted and never shows the secret again: not to you, not to a chat, not to any agent. Set your own monthly limit there too. You can replace or remove them at any time.
  2. Approve flo2-rvt's one-time setup on your app. The first time you ask your chat for a cloud-Revit job, flo2 checks your app, finds flo2-rvt is not on it yet, and offers to set it up. flo2.io does it for you with the keys you stored: nothing runs on your computer. You approve it on flo2.io the way you approve a job, shown exactly what it does on your app: it keeps your app's nickname if it has one, and otherwise sets no nickname (your app is then named by its client id, which Autodesk always accepts), uploads flo2-rvt's Revit add-in, creates its probe and edit jobs on the Revit 2024 engine, and sets Autodesk's own monthly limit on processing time for your app, from your flo2.io limit in whole hours. That limit is a hard stop at Autodesk, whatever happens in flo2. The setup deletes nothing, costs no processing time, and is recorded in your design. When a new flo2-rvt brings a new add-in, flo2 asks again. flo2-rvt's README says what it does there, call by call.
  3. Use it. Ask your chat to probe a Revit file in your design. Before any paid job runs, flo2 checks your app is set up, then asks you to confirm the job, with its expected processing time, and every job is recorded in the design it ran for.

The probe opens your file and changes nothing in it. It gives back a report of the model's levels, sheets and linked files, every sheet as one PDF, and an IFC from Autodesk's own exporter, each kept as a new file in your design.