Automated Copyt Authentication Hold Tracking
Every hour, WebRun opens Copyt, finds pairs sitting on an authentication hold, checks the verification status on StockX, logs each case to Google Sheets, and posts Slack any hold that needs your response.
How do I keep track of sneaker authentication holds that need a response?
Every hour, WebRun opens Copyt to find pairs sitting on an authentication hold, then checks the verification status and reason on StockX. It logs each case to Google Sheets and posts Slack any hold that needs a response, so authentication problems get resolved fast instead of sitting unresolved for days.
- Authentication holds get flagged within the hour, not discovered days later
- Every hold keeps a full status history, useful for repeat or disputed cases
- Appeals and responses stay with your team, nothing is submitted automatically
Built for sneaker resellers · StockX sellers · streetwear resale shops
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
connect.copyt.ioin a real browser with your saved login - no setup, no API keys. -
1
Copyt - find pairs on an authentication hold
copyt.io
WebRun opens Copyt to find pairs on an authentication hold. - Open Copyt and filter shipped pairs to authentication hold status
- Capture the pair, ship date, and days on hold for each
- Note any hold already resolved since the last check
Done when Every pair on hold is listed with its ship date and days waiting.
-
2
StockX - check the verification status
stockx.com
WebRun opens StockX to check the verification status. - Check StockX for the verification status and reason on each held pair
- Note whether it needs more photos, an appeal, or is awaiting review
- Flag any hold that has turned into a rejection
Done when Every hold's reason and current status is confirmed on StockX.
-
3
Google Sheets - log each hold case
google.com
WebRun opens Google Sheets to log each hold case. - Log each hold case with its status, reason, and days open
- Update the log when a hold resolves or turns into a rejection
- Keep a running history for disputed or repeat cases
Done when Every hold case is logged with a current status and history.
-
4
Slack - flag holds needing action
slack.com
WebRun opens Slack to flag holds needing action. - Post an alert for any hold needing action, like more photos or an appeal
- Flag rejections and long-running holds first
- Leave the appeal or response to your team to submit
Done when Your team has a clear action list for every open authentication hold.
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 submit an appeal or respond to the marketplace for me?
No. It only checks the status and flags what's needed. Submitting photos, an appeal, or a response is left to your team, since that decision needs a person's judgment.
How does it tell a hold from a rejection?
It reads the actual verification status and reason on StockX, so a pair still under review is flagged differently from one that has actually failed authentication and needs an appeal.
Why keep a log in Google Sheets as well as a Slack alert?
The Slack alert is for what needs action right now. The Google Sheets log keeps a full history, useful if a pair or a marketplace keeps generating repeat holds.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.