Automated Weaviate Index Sync Checks
Every night, WebRun checks Google Drive for documents added that day, confirms each one has a matching object in Weaviate, flags anything that failed to embed or index, and reports the sync status to Slack so a missing document gets caught the same day.
How do I check that new Drive documents are indexed in Weaviate?
WebRun checks Google Drive every night for documents added that day, then confirms each one has a matching indexed object in Weaviate. It flags anything that failed to embed and reports the sync status to Slack, so a missing or failed document gets caught the same day instead of during a search that comes up empty.
- Missing or failed documents get caught the same night
- Every sync check ends in a clear pass or fail report
- Nobody discovers a gap only when a search comes up empty
Built for AI engineering teams · data engineering teams · RAG application developers · ML platform 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
console.weaviate.cloudin a real browser with your saved login - no setup, no API keys. -
1
Google Drive - list documents added today
drive.google.com
WebRun opens Google Drive to list documents added today. - Open the source folder and list documents added today
- Capture the file name and folder for each
- Note the total count expected to be indexed
Done when Every document added today has been listed.
-
2
Weaviate - confirm each one is indexed
weaviate.io
WebRun opens Weaviate to confirm each one is indexed. - Open the Weaviate console and query the collection for today's objects
- Match each Drive document against an indexed object
- Flag any document with no matching object or a failed embed
Done when Every document from today has been checked against the index.
-
3
Slack - report the sync status
slack.com
WebRun opens Slack to report the sync status. - Post the sync status to the data channel with counts indexed and missing
- List any document that failed to embed by name
- Keep the report internal to your team
Done when The team has today's sync status 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 it re-index the documents that failed automatically?
No. It only detects and reports what failed to embed. Re-indexing or fixing the pipeline is a decision for your engineers.
Does it read the contents of my documents?
It only checks whether a document has a matching indexed object, it does not need to read or expose the document's contents to do that.
What if no new documents were added that day?
The Slack report still posts and simply confirms there was nothing new to check, so you know the job ran.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.