CHATBOTS

Scheduled Gradual Ramp Executor for Feature Flags

Runs on a schedule, reads due ramp stages from Postgres, pushes the next percentage to Vercel Edge Config, and posts each advance to Slack.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled tick
  • ActionFetch due ramp stagesPostgreSQLPostgres
  • LogicSkip paused or rolled-back flags
  • ActionPush next percentage to Vercel Edge ConfigVercelVercel
  • ActionMark stage appliedPostgreSQLPostgres
  • OutputAnnounce each advance in SlackSlack

What it does

Executes the ramp plans that a rollout bot scheduled earlier. On each tick it finds flag stages whose advance time has arrived, raises the live percentage to the next step, propagates the value to Vercel Edge Config so apps read it at the edge, and announces the change. This is the deterministic engine that actually moves flags from 5% to 25% to 100% over time.

When to use it

When you have approved, staged ramp plans sitting in Postgres and want them advanced automatically and safely, with each step broadcast to the team instead of done by hand.

How it works

  1. 1A schedule fires (for example every 15 minutes).
  2. 2The pipeline queries Postgres for ramp stages whose scheduled time has passed and are not yet applied.
  3. 3For each due stage it branches on whether a prior stage was paused or rolled back, skipping flags that are on hold.
  4. 4It writes the new percentage to Vercel Edge Config and marks the stage applied in Postgres.
  5. 5It posts a per-flag advance notice to Slack with old and new percentages.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect VercelDeploys, runtime logs, analytics.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.