PSS Pipeline Steps Solutions

Wiki-style operator notes

How the MVP setup is meant to look.

The Flow site connection is configured once per tenant. Each selected Flow project then receives its own automation installations. Public webhook URLs are shown only where real customer-facing ingress exists.

Flow site foundation Site URL Script name + API key pair Pipeline Step Project installations Webhook endpoints Secret references Customer-visible targets Slack delivery Status-driven project behavior Bundled internal follow-ups Task-ready notifications Routing snapshot refresh

Version Review to Slack

Install this on a project when review-ready Versions should post into Slack with a public Flow webhook endpoint.

  • Confirm the site foundation first. The row inherits the account Flow URL and script pairing.
  • Enter a Slack bot token only if the current installation is not already connected.
  • Use the row help panel to confirm the public webhook URL before creating the Flow trigger.

Version Update Trigger

Use the status map to convert Version state into Task state inside a selected Flow project.

  • Load statuses after selecting a project so the mapping is project-specific.
  • Leave unmapped Version statuses blank when they should not affect the Task.
  • Remember that saved values cannot be rehydrated from the current canonical list response yet.

Ready Task Notifications

This product is customer-visible, but its trigger path is bundled with Task Dependency Status instead of exposing a fake public endpoint.

  • Set the Slack identity field or enable email lookup for assignee resolution.
  • Choose which Task statuses count as ready for a direct notification.
  • The workspace labels the trigger as bundled internal follow-up, not a separate webhook.

Task Dependency Status

This installation updates downstream Task state and may trigger the bundled ready-task notification path.

  • Configure waiting, ready, and unblocking Task statuses against the selected project catalog.
  • Public webhook setup is available in the row help and endpoint summary.
  • The fixed runtime follow-up delay policy is not customer-configurable in MVP.

Notes and Replies

Notes and replies stay one bundled product even though the runtime uses separate note and reply endpoints.

  • Configure Slack delivery once for the installation.
  • Set attachment retry delays and match window if your project needs a different review cadence.
  • Create both public Flow triggers from the row help if the project is using Notes and replies.