All projects
Autodesk's Flow Graph Engine n8n Automation

Autodesk's Flow Graph Engine n8n Automation

archived

A low-code Flow Graph Engine (FGE) job queue built in n8n — submit tasks via forms or webhooks, monitor progress on a dashboard, and get email or Slack alerts when jobs finish.

n8nautodesk-apsFGEbifrostUSDautomationlow-codewebhooksemail

What it does

An n8n workflow that automates Autodesk's Flow Graph Engine (FGE) job submission and monitoring without writing a custom server. Import the workflow, connect your APS credentials, and drive the full pipeline from a form or webhook trigger.

  • Task submission via n8n forms or inbound webhooks — upload USD scenes and Bifrost graph files
  • Job monitoring through n8n's execution dashboard — poll FGE status, branch on SUCCEEDED / FAILED / CANCELLED
  • Notifications via email (and Slack-ready n8n nodes) when jobs complete, fail, or produce output artifacts
  • End-to-end APS integration: OAuth authentication, OSS upload URLs, file completion, job submit, log fetch, and output download

Why I built it

Built as the live demo for my Autodesk University 2025 talk — to show that Flow Graph Engine orchestration doesn't require a bespoke backend. n8n's visual workflow editor makes APS + FGE accessible to pipeline TDs and automation engineers who prefer low-code over rolling their own queue service.

How it works

  • Platform: n8n workflow: 40+ nodes wiring HTTP, code, switch, wait, and merge steps
  • APS APIs: two-legged OAuth token fetch, OSS signed upload URLs, multipart file upload completion
  • FGE APIs: submit Bifrost graph jobs, poll job status in a loop, fetch batch logs and output USD files
  • Triggers: n8n Form Trigger for manual submission; webhook-compatible for upstream system integration
  • Notifications: email send nodes on terminal states; Slack nodes available via standard n8n integrations

What I learned

Visual workflow tools shine for conference demos — you can walk an audience through every API call on screen. The trade-off is state management: FGE's multi-step upload + poll + download flow needs careful env passing between nodes, which is where embedded Code nodes earn their keep in n8n.