Automated Locket Photo Drop Recap
Every night, WebRun opens Locket, checks which photos went out to your widget audience that day and how they reacted, archives each photo to Google Drive, and posts a short recap to Slack so the team can see what landed.
How do I keep a record of the photos I send through Locket?
WebRun checks Locket every night for the photos sent to your widget audience that day, archives each one to Google Drive with its caption and date, and posts the team a short recap in Slack with the day's top-reacted photo. It never sends a photo through Locket itself, so every send stays a personal choice.
- Every Locket photo is archived instead of disappearing into the app
- The team sees what landed without opening Locket themselves
- A searchable photo history builds automatically in Drive
Built for Creators · brand social teams · influencer managers · community 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
locket.camin a real browser with your saved login - no setup, no API keys. -
1
Locket - check today's photo drops and reactions
locket.cam
WebRun opens Locket to check today's photo drops and reactions. - Open Locket and review the photos sent today
- Note the caption, send time, and reaction count for each
- Flag the photo with the strongest reaction
Done when Every photo sent today has its reactions recorded.
-
2
Google Drive - archive each photo
drive.google.com
WebRun opens Google Drive to archive each photo. - Open the Locket archive folder in Google Drive
- Save each photo with its caption and date in the filename
- Keep the folder organized by month
Done when Every photo sent today is archived with its details.
-
3
Slack - post the recap
slack.com
WebRun opens Slack to post the recap. - Post today's photo count and the top-reacted photo to the team channel
- Include the reaction totals
- Link to the archived photos in Drive
Done when The team has today's recap posted in Slack.
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
Does WebRun send photos through Locket for me?
No. It only reads photos that have already been sent. Choosing and sending each photo through Locket is still up to you.
Why archive the photos separately?
Locket doesn't keep a browsable history, so archiving each send to Drive gives you a permanent, searchable record of what went out and when.
Will the whole team see every photo in Slack?
Just the recap with the count and the top-reacted photo. The full archive lives in Drive if someone wants to look closer.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.