Pipeline Steps Solutions

Implementation guide

Set up one automation at a time.

Start with the shared Flow site connection, then use the automation sections below for the Flow webhook values, Pipeline Steps fields, and customer check needed for each automation.

Shared foundation

Flow site URLYour Flow Production Tracking site, for example https://studio.shotgunstudio.com.
Script nameThe Flow script user that Pipeline Steps Solutions uses for API reads and writes.
API keyThe matching API key for that script user. This is stored as a secret and is never shown again.
ProjectsSelect only the Flow projects that should have customer-visible automation installs.

Flow webhook pattern

  1. Open the automation in Pipeline Steps Solutions and go to Config.
  2. Copy the Webhook URL.
  3. Click Rotate and show secret once, then copy the signing secret before leaving the page.
  4. In Flow, create a webhook destination for the selected project.
  5. Paste the Pipeline Steps URL into the webhook URL field.
  6. Paste the signing secret into Flow's secret or signature field.
  7. Select the event values listed in that automation's section below.
  8. Save the Flow webhook and send a test delivery when Flow offers one.

Slack bot setup

Token typeUse the Bot User OAuth token from Slack OAuth & Permissions. It starts with xoxb-. Do not use an xapp- token.
Required bot scopesGrant this full shared set when one Slack app is used across the Pipeline Steps automations: channels:manage, channels:read, chat:write, files:read, files:write, groups:write, im:write, mpim:write, users:read, users:read.email.
Ready Task NotificationsEmail lookup is now the default. The Flow HumanUser email must match the Slack account email, and users:read.email must be granted for Slack lookup to succeed.
After changing scopesReinstall the Slack app to the workspace, copy the new xoxb- token, then save that token back into the automation Config panel.

Shared automation knowledge

Project scopeEach automation runs only for the Flow project installation selected in the workspace.
Managed webhooksPipeline Steps creates or updates Flow webhooks from the automation Config footer. Webhook secrets stay write-only.
Slack tokenSlack automations use a Bot User OAuth token. Reinstall the Slack app after changing scopes, then save the new token.
ValidationAfter setup, send a focused Flow test event and confirm one expected downstream result before enabling broader rollout.

Version Review to Slack

Posts Flow Version review activity into the Slack channel selected by your routing rules.

Slack bot tokenUse the Bot User OAuth token from Slack OAuth & Permissions. It starts with xoxb-.
Routing rulesRules decide the Slack channel from Flow group, asset type, task name, pipeline step, status, or special access.
Flow entity and eventsVersion created and Version updated.
FieldsUse no field filter, or include sg_status_list plus the thumbnail/image fields your studio uses to mark review-ready Versions.
  1. Create or update a test Version in Flow.
  2. Confirm one Slack message appears in the expected channel.
  3. Send the same webhook test again and confirm it does not double-post the same Version.

Version Update Trigger

Turns selected Version status changes into Task status updates on the linked Flow Task.

Version to Task status mapChoose which Version statuses change the linked Task status.
Parent complete statusOptional. For Assets this can be fin when a completed parent should be recognized as finished.
Flow entity and eventVersion updated.
Fieldsg_status_list.
  1. Pick a Version linked to a Task.
  2. Change the Version status to a mapped value.
  3. Confirm the linked Task moves to the mapped Task status.

Task Dependency Status

Moves downstream Tasks when upstream Task work reaches a configured unblocking state.

Waiting statusesTask statuses that mean downstream work is blocked.
Ready statusesTask statuses that downstream work should move into when dependencies clear.
Unblocking statusesUpstream Task statuses that count as complete enough to release downstream work.
Flow entity and eventTask updated on sg_status_list.
  1. Create or choose an upstream Task and a downstream dependent Task.
  2. Put the downstream Task in a waiting status.
  3. Move the upstream Task into an unblocking status.
  4. Confirm the downstream Task moves into the expected ready status.

Ready Task Notifications

Sends a Slack notification when Task Dependency Status makes a Task ready for its assignee.

Public webhookNone. This automation runs from the Task Dependency Status path.
Slack bot tokenUse the Bot User OAuth token from Slack OAuth & Permissions. It starts with xoxb-.
Ready statusesTask statuses that should trigger a ready notification.
Email lookupThe Flow HumanUser email must match the Slack account email for the assignee.
  1. Use Task Dependency Status to release a downstream Task.
  2. Confirm the Task moves into a configured ready status.
  3. Confirm the Flow assignee email matches the Slack account email for that person.
  4. Confirm the assignee receives one Slack notification.

Notes and Replies

Uses one Flow webhook to send both new Notes and new Replies into Slack with attachment follow-up.

Slack bot tokenUse the Bot User OAuth token from Slack OAuth & Permissions. It starts with xoxb-.
Attachment match windowHow long attachment timing can differ from the Note or Reply and still be matched.
Flow entities and eventsNote created and Reply created.
DestinationUse the same Pipeline Steps webhook URL for both events.
  1. Create a Note on a Version that matches a routing rule.
  2. Confirm one Slack message appears in the expected channel.
  3. Create a Reply on that Note.
  4. Confirm the Reply posts from the same webhook setup.
  5. Add an attachment and confirm it appears after processing or after the configured retry delay.