Autodesk Flow Production Tracking automation

Keep studio work moving without babysitting status updates.

Pipeline Step connects Flow events, task states, versions, notes, and Slack notifications so producers, supervisors, and artists know what is ready next.

Film review notes, versions, and dailies routing
VFX task readiness, dependency changes, and Slack delivery
Games asset status, milestone signals, and production handoffs

What it automates

The right update reaches the right place.

Route Flow activity to Slack, keep task statuses aligned, notify assignees when work becomes ready, and map each studio's version statuses to the workflow that actually runs the show.

Versions

Review posts with context

Send version updates, thumbnails, task names, descriptions, and Flow links to the right Slack channels.

Tasks

Ready-to-start signals

Notify artists when upstream work unblocks their task, without asking production to chase every dependency.

Status

Studio-specific mapping

Match Flow version and task statuses to the labels each department already understands.

Routing

Project-aware delivery

Use project, task, asset type, pipeline step, group, and visibility rules to keep messages focused.

A production team reviewing work together in a modern studio setting

Daily workflow

Less checking, more producing.

  1. 1Flow sends a signed webhook.
  2. 2Pipeline Step validates the studio, site, project, and automation.
  3. 3The job runs asynchronously with tenant-scoped credentials.
  4. 4Slack and Flow updates are logged with audit-friendly context.

Guided setup

A clear path from kickoff to first automation.

The onboarding flow walks each studio through implementation planning, Flow connection, Slack installation, project selection, status mapping, webhook testing, and activation.

01

Open workspace

Sign in so the studio admin workspace is ready for implementation.

02

Connect Flow

Enter the site URL and securely save API script credentials.

03

Add Slack

Install the Slack app with OAuth and validate required scopes.

04

Map statuses

Match version and task statuses to the studio workflow.

05

Test webhooks

Confirm signed deliveries before automations go live.

Security posture

Built for studio trust from the first deployment.

Customer credentials belong in encrypted secret storage, never in public pages, email threads, logs, or shared configuration files.

Tenant isolation

Every webhook, job, receipt, and audit event carries tenant, site, and project context.

Encrypted credentials

Flow API keys, Slack tokens, billing secrets, and webhook secrets are stored in AWS Secrets Manager.

Signed webhooks

Flow deliveries are verified with per-endpoint secrets before jobs are accepted.

Billing boundary

Billing and service changes stay inside authenticated admin workflows instead of public forms.

Packages

Start simple, scale by studio coverage.

Setup and recurring service are scoped around implementation, support, and active project coverage rather than self-serve seats.

Foundation

$5,000 setup + $1,900/month

For small studios running 1-2 active projects with a managed rollout.

  • 1 Flow site
  • 2 active projects
  • Five core automations
  • Managed setup, testing, and bounded support
Start Foundation

Concierge

$15,000 setup + $6,000/month starting

For midsize studios that want higher-touch rollout help and priority support.

  • Priority support and dedicated Slack channel
  • Quarterly workflow audit
  • Higher change budget and rollout coordination
  • Separately scoped custom automation
Start Concierge

Early access

Bring the first automation online with a guided setup.

Tell us the studio size, the Flow site count, and the first workflow you want to automate. No API keys or tokens belong in this form.

This demo form does not submit yet. The production app will route this through the authenticated backend.