Automated Neptune.ai Project Setup Checklist
Every Monday, WebRun opens Neptune.ai, reviews projects created in the past week, checks whether required metadata tags and naming conventions are set up on their runs, logs any gap to a Google Sheet, and posts a Notion setup checklist so new projects start out consistent with the rest of the workspace.
How do I make sure new Neptune.ai projects follow our tagging standard?
WebRun reviews Neptune.ai projects created each week, checking whether their runs use the team's required metadata tags and naming convention, and logs any gap to a Google Sheet. It then posts a Notion setup checklist naming each new project and what it still needs, so a new ML project starts out consistent instead of drifting from the workspace standard.
- New projects start consistent instead of drifting from team conventions
- Missing setup gets caught within a week instead of after runs pile up
- Project owners see exactly what is missing instead of guessing
Built for ML engineering teams · data science teams · MLOps teams · research leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.neptune.aiin a real browser with your saved login - no setup, no API keys. -
1
Neptune.ai - check new project setup
- Open Neptune.ai and review projects created in the past week
- Check whether runs are using the team's required metadata tags and naming convention
- Note any project missing the standard setup
Done when Every new project's tagging and naming setup is checked against the team standard.
-
2
Notion - log setup gaps
notion.so
WebRun opens Notion to post the setup checklist. - Open the ML team's Notion page
- Post this week's checklist naming each new project and what setup it still needs
- Assign it to the project owner if known
Done when The team has this week's project setup checklist in Notion.
-
3
Google Sheets - post the setup checklist
google.com
WebRun opens Google Sheets to log setup gaps. - Open the Neptune Project Setup sheet
- Add a row per new project noting what setup is missing
- Mark any project completed since the last check as done
Done when The sheet reflects the current setup gap for every new project.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will WebRun add the tags or rename runs itself?
No. It only checks what is missing and builds the checklist. Adding metadata tags or renaming runs stays with the project owner.
What counts as required metadata?
Whatever tagging and naming convention your team has already standardized on, such as owner, model type, or dataset version tags.
Does it check older projects too?
It focuses on projects created in the past week, since that is when a missing convention is easiest to fix before runs pile up.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.