Automated Arc.dev Candidate Follow-Up
Every morning, WebRun opens Arc.dev, walks each open role, finds the candidates stuck waiting on your team for feedback, an interview slot, or a decision, updates the matching row in your Notion hiring tracker, and creates a Trello card for anyone who has waited longer than your limit.
How do I stop developer candidates from going cold in my pipeline?
WebRun opens Arc.dev every morning, walks each open role, and finds the candidates waiting on your team for feedback, an interview, or a decision. It updates your Notion hiring tracker and raises a Trello card for anyone past your response window, so good developers stop going cold.
- Candidates stop waiting days for a decision
- The hiring tracker matches reality every morning
- Every stalled candidate has one owner and one card
Built for engineering managers · technical recruiters · startup founders · remote-first teams
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
arc.devin a real browser with your saved login - no setup, no API keys. -
1
Arc.dev - find candidates waiting on you
WebRun opens Arc.dev to find candidates waiting on you. - Open Arc.dev and list every active role you are hiring for
- For each role, capture the candidates in progress and the stage they sit in
- Work out how many days each candidate has been waiting on your side
- Flag anyone past the response window you set, usually three working days
Done when Every in-progress candidate has a stage and a days-waiting number.
-
2
Notion - update the hiring tracker
WebRun opens Notion to update the hiring tracker. - Open your hiring tracker database in Notion
- Update the stage, last activity date, and days waiting on each candidate row
- Add a row for any candidate that is not tracked yet
- Set the status property to stalled for anyone past the response window
Done when The Notion tracker matches the live Arc.dev pipeline.
-
3
Trello - raise a card per stalled candidate
WebRun opens Trello to raise a card per stalled candidate. - Create one Trello card per stalled candidate on your hiring board
- Title it with the candidate, the role, and the days waiting
- Put the next action in the description: send feedback, book the call, or decline
- Skip anyone who already has an open card so the board does not fill with duplicates
Done when Every stalled candidate has exactly one open Trello card.
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 it message or reject candidates for me?
No. WebRun never contacts a candidate and never declines anyone. It only updates your internal Notion tracker and Trello board so a human takes the next step.
How long before a candidate counts as stalled?
Three working days by default, and you can set any window per role. Only candidates waiting on your side of the process are counted.
Will the Trello board fill up with duplicates?
No. WebRun checks for an existing open card before it creates one, so each stalled candidate has exactly one card until you close it.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.