Version Review to Slack
Posts Flow version updates into Slack with project-aware routing.
Autodesk Flow Production Tracking operations
Customer setup stays clean. Runtime work stays invisible.
Configure one Flow site, install the exact project automations you need, and keep version reviews, task readiness, dependency status, and notes moving without exposing internal Lambda or AWS details to customers.
Locked MVP
5 customer-visible automations
Setup boundary
Flow site at account level, installs at project level
Integrations
Slack only for MVP configuration
Customer-visible surface
Only the locked automation set appears in the workspace.
The admin UI renders the exact five MVP automations and keeps bundled internal behavior labeled as bundled instead of pretending it is a separate customer endpoint.
Version Update Trigger
Maps Version statuses to Task statuses using project-specific rules.
Ready Task Notifications
Handles Slack notifications when downstream work becomes ready.
Task Dependency Status
Tracks upstream completion and updates dependent task state.
Notes and Replies
Relays Notes and replies without splitting them into fake extra products.
Operational flow
Onboarding is explicit, project installs stay deliberate.
The workspace asks for the Flow foundation once, discovers available projects, and only installs automations on the projects an admin explicitly selects.
- Connect the Flow site Save site URL, script name, and a write-only API key pair.
- Discover projects Review the projects returned by Flow before importing anything.
- Install per project Each project gets its own automation installations and webhook endpoints.
- Operate from one shell Toggle status, review health, rotate secrets, and open setup help from the same workspace.
Workspace shape
- Left-icon nav for Site Config, Automations, Billing, Health, Security, and Support
- Automation rows show only name, Flow URL, and on/off state by default
- Config, log, and help expand inline under the selected row
- Detailed raw logs stay hidden unless a real backend route exists
Security posture
Secret entry is allowed. Secret redisplay is not.
The frontend keeps API keys and integration tokens write-only, avoids browser persistence drift, and shows only public webhook URLs or customer-safe summaries.
Write-only secret intake
API keys and Slack tokens are entered, posted, and immediately cleared from the form.
Customer-safe summaries
Secret references, endpoint ids, and timestamps are visible. Raw secret values are never rendered.
Public webhook discipline
Only real `/r/{endpoint_id}` ingress URLs are shown. Bundled internal behavior is labeled clearly.
Audit-aware UI
Security and audit sections show summaries or blocked states, not invented raw-log browsers.