AI AGENTS
Repricing Proposal Queue with Human Approval in Linear
An agent gathers competitor prices, drafts repricing recommendations with rationale, and files each as a Linear issue so a manager can approve or reject before any price changes.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled proposal run
- ActionRead watchlist and margin policy from PostgresPostgres
- ActionAgent captures competitor pricesBrowserbase
- LogicCompute recommended price; drop SKUs within tolerance
- ActionFile each recommendation as a Linear issueLinear
- OutputPost approval-queue summary to SlackSlack
What it does
Turns raw competitor price observations into reviewable repricing proposals. The agent browses the tracked storefronts, computes a recommended new price per SKU using your margin rules, and writes each recommendation as a structured Linear issue containing the current price, competitor price, proposed price, and the reasoning. Nothing changes automatically; the queue is the control point.
When to use it
Use it when pricing changes require sign-off and you want an auditable paper trail of why each move was proposed. Good for teams that treat repricing as a reviewed decision, not an automatic one.
How it works
- 1A schedule kicks off the proposal run.
- 2The agent reads the watchlist and your margin policy from Postgres.
- 3Browserbase captures each competitor's live price.
- 4A logic step computes a recommended price and discards SKUs already within tolerance.
- 5For each remaining SKU the agent opens a Linear issue with full rationale and a proposed value, tagged to the pricing team.
- 6A Slack summary links the new approval queue so reviewers know work is waiting.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.