DEVOPS

Slack-approved pause for idle Hugging Face Spaces

On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.

CategoryDevOps
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule starts idle scan
  • ActionList paid Spaces with idle timeHugging FaceHugging Face
  • LogicKeep Spaces idle past threshold
  • OutputPost interactive Slack approval requestSlack
  • ActionPause Space on approvalHugging FaceHugging Face
  • ActionLog decision to GitHub audit issueGitHubGitHub

What it does

Finds idle Hugging Face Spaces on paid hardware and, instead of pausing them automatically, asks for a human yes-or-no in Slack. When the owner approves, it pauses the Space and records who approved and when in a GitHub issue so there is a clean audit trail.

When to use it

When some Spaces are sensitive enough that auto-pausing is risky, but you still want idle compute flagged daily and paused with one click plus a paper trail.

How it works

  1. 1A daily schedule starts the scan.
  2. 2List paid-hardware Spaces and their idle time via the Hugging Face API.
  3. 3A filter keeps Spaces idle past the threshold.
  4. 4Post an interactive Slack approval message per candidate showing tier, idle time, and projected savings.
  5. 5On approval, call the Hugging Face API to pause the Space.
  6. 6Append the decision (Space, approver, timestamp) to a GitHub audit issue.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  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.