Review posts with context
Send version updates, thumbnails, task names, descriptions, and Flow links to the right Slack channels.
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.
Ready-to-start signals
Notify artists when upstream work unblocks their task, without asking production to chase every dependency.
Studio-specific mapping
Match Flow version and task statuses to the labels each department already understands.
Project-aware delivery
Use project, task, asset type, pipeline step, group, and visibility rules to keep messages focused.
Daily workflow
Less checking, more producing.
- 1Flow sends a signed webhook.
- 2Pipeline Step validates the studio, site, project, and automation.
- 3The job runs asynchronously with tenant-scoped credentials.
- 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.
Register
Start with a verified account and a studio workspace ready for setup.
Connect
Securely link your Flow site so Pipeline Steps can read the events your automations need.
Configure
Choose projects, statuses, destinations, and routing rules that match the way your studio works.
Integrate
Connect production applications so updates land in the right place.
Monitor
Review deliveries, webhook health, and automation activity.
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, payments secrets, and webhook secrets are stored in AWS Secrets Manager.
Signed webhooks
Flow deliveries are verified with per-endpoint secrets before jobs are accepted.
Payments boundary
Payments and service changes stay inside authenticated admin workflows instead of public forms.
Plans
Choose the rollout fit that matches your studio scope.
Plans are scoped around implementation depth, project coverage, and operating support so studios can start cleanly and expand with confidence.
Foundation
Best for smaller teams bringing one Flow site and a focused first automation package online.
- 1 Flow site
- 2 active projects
- Five core automations
- Managed setup, testing, and bounded support
Studio
Most usefulBest for studios standardizing Flow-to-Slack and task automation across multiple active productions.
- 1 Flow site
- Up to 5 active projects
- Core automations with richer routing support
- Monthly workflow review and faster support
Concierge
Best for operators who want a higher-touch rollout, tighter coordination, and priority support coverage.
- Priority support and dedicated Slack channel
- Quarterly workflow audit
- Higher change budget and rollout coordination
- Separately scoped custom automation
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.