WorkerKitJoin the waitlistAI workers for Collection
AI workers for collection gather items scattered across Gmail, Drive, and Slack into one place on a schedule. WorkerKit controls exactly which sources they can pull from and what they may read.
- CRM Scribe Language model Logs your meetings and email threads into the CRM so records stay current without manual data entry.
- Meeting Action Item Collector Language model Reads your meeting notes each evening and files every action item into your task board.
- SEO Watchtower Language model Watches Search Console weekly for ranking drops, indexing problems, and easy CTR wins, and files the fixes.
- Company Knowledge Concierge Language model Answers questions from your Drive, SharePoint, and Slack history, with citations to the source.
What is a Collection AI worker?
A collection AI worker is an AI agent set up to run the collection job unattended, pulling related items from several sources and assembling them into one list, folder, or record. It typically touches Gmail and Outlook attachments, Google Drive and SharePoint files, Slack and Microsoft Teams messages, and CRM records, gathering only from the sources and fields you have approved.
What these workers do
Gather invoice attachments from Outlook
Pulls PDF and spreadsheet attachments from matching Outlook messages each week and drops them into a single SharePoint folder for the finance team to reconcile.
Collect design links from Slack
Scans chosen Slack channels for shared Figma and Google Drive links, then compiles them into one Notion page so nothing gets lost in scrollback.
Assemble deal files from Google Drive
Finds documents tied to a named HubSpot deal across Google Drive and gathers them into a single folder so anyone joining the account has the full history.
Round up receipts from Gmail
Reads Gmail for expense receipts over a period, extracts the attachments, and stacks them in one Drive folder ready for an expense report.
How a Collection AI worker runs
What it connects to
When it runs
What stays under your control
Collection questions, answered.
What sources can a collection AI worker pull from?
Only the apps and locations you connect and approve. A collection worker can gather from Gmail, Outlook, Google Drive, OneDrive, SharePoint, Slack, or Microsoft Teams, but WorkerKit scopes it to the exact folders and channels you grant. It reads those sources and writes only to the single destination you choose, nothing wider.
Does a collection worker move files or just copy them?
It copies matching items into your destination and leaves the originals in place, unless you grant move or delete permission. A collection worker's default job is to assemble, not to clear out. If you want it to also remove gathered originals, that is a separate write permission you turn on in WorkerKit.
Can a collection worker gather from a single Drive folder only?
Yes, per-entity scope binds it to exactly the folders you name. When you set up a collection worker you can restrict it to one Google Drive or SharePoint folder, and the firewall blocks every file outside that scope. This keeps a gather job narrow even when the wider drive holds sensitive material.
Will a collection worker see attachment contents?
Only if you grant it read access to the file body, and you can redact fields first. A collection worker often needs just the attachment itself, so you can let it copy files without exposing your other documents. WorkerKit records every item it gathers so you can confirm exactly what was pulled.