AI AGENTS

Replicate Deprecation Webhook Triage to PagerDuty and GitHub

Receives Replicate deprecation webhooks in real time, classifies blast radius across your pinned endpoints.

CategoryAI Agents
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReplicate deprecation webhook receivedHTTP webhook
  • ActionQuery Postgres for endpoints pinning the version and trafficPostgreSQLPostgres
  • LogicBranch on call volume to assign severity
  • ActionOpen PagerDuty incident for high-severity pathPagerDutyPagerDuty
  • ActionOpen GitHub backlog issue for low-severity pathGitHubGitHub
  • OutputPost routing decision to SlackSlack

What it does

This pipeline turns a Replicate deprecation notice into an instant, severity-aware response. When a webhook arrives, it cross-references the deprecated version against a live inventory of which endpoints still pin it and how much traffic they carry, then routes the event to PagerDuty for hot paths or to a GitHub backlog issue for low-volume ones.

When to use it

Use it when you cannot wait for a daily sweep — a deprecated version on a high-traffic endpoint needs an on-call human now, while a rarely used one just needs a tracked task.

How it works

  1. 1A Replicate deprecation webhook hits the inbound endpoint.
  2. 2The pipeline queries Postgres for every endpoint pinning the deprecated version plus its 7-day call volume.
  3. 3A logic branch compares volume against a threshold to set severity.
  4. 4High severity triggers a PagerDuty incident routed to the inference on-call.
  5. 5Low severity instead opens a GitHub issue labeled migration-backlog with the affected endpoints.
  6. 6Either path closes by posting the routing decision to Slack for visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Connect GitHubRepos, issues, pull requests, actions.
  5. 5
    Connect SlackChannels, DMs, threads, mentions.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.