Send WorkerKit reports to OpenAI Dots via email.
Give a recurring job to a WorkerKit worker, send its report to the personal email account connected to your dot, and ask the dot to review it. This uses documented email capabilities on both sides, without assuming Dots already has a WorkerKit plugin.
Before you start
What you need.
A WorkerKit account, a worker, and a Google or Microsoft mailbox connected to WorkerKit for email notifications. You can install a ready-made kit from the directory or configure an existing worker.
Access to a dot. OpenAI begins setup on desktop web or in the desktop app; rollout is gradual and eligibility depends on plan and market.
A personal email account that you can connect to your dot and use as the worker report recipient. The dot does not have its own standalone email address at launch.
| What | Address | Why |
|---|---|---|
| Dots launch | https://openai.com/index/introducing-dots/ | OpenAI's product announcement, including rollout and the current feature set. |
| Dots help | https://help.openai.com/en/articles/20001530-getting-started-with-your-dot | OpenAI's setup, connected apps, activity and approval instructions. |
| Kit directory | https://workerkit.ai/kits | Find a ready-made worker for the job you want to run. |
| Connected apps | https://workerkit.ai/apps | Connect a Google or Microsoft mailbox so WorkerKit can send email notifications. |
| Your workers | https://workerkit.ai/workers | Review the worker, its schedule, notifications and run history. |
| Skill file | https://workerkit.ai/dots/SKILL.md | The tool reference and the operating rules the agent keeps after setup. |
| This guide as markdown | https://workerkit.ai/dots/setup.md | The same steps, for an agent that reads markdown rather than a page. |
OpenAI says Dots use plugins and connected apps. It has not established that these WorkerKit MCP mounts can be added to a dot, so the steps below use a route both products actually expose: WorkerKit email delivery and a personal mailbox connected to the dot.
Do not paste a WorkerKit manager key into a dot conversation. A message is not an authentication setting. This route needs no fleet credential in Dots, and it does not grant the dot WorkerKit management tools.
The case for connecting at all is on the OpenAI Dots page.
Step 0. Human
Create your dot and connect email.
Create the dot on desktop, then connect the personal mailbox that will receive worker reports.
- 01
Create a dot on desktop
In ChatGPT desktop or desktop web, create your primary dot and follow the onboarding prompts. If the entry point has not appeared, OpenAI says rollout can take several days on an eligible account.
- 02
Connect your personal email
In the dot's profile, review Plugins and connect a supported personal email app with the permissions you are comfortable granting. OpenAI says available apps may differ by account. The dot has no standalone mailbox at launch.
- 03
Check access
Ask your dot to find a harmless message already in that mailbox. If it cannot, fix the app connection before sending a WorkerKit report.
Follow OpenAI's getting started guide for the current screens and supported app list.
Step 1. Human
Choose one repeatable job.
Install a kit or select an existing worker, then review its instruction, app access, schedule and budget.
- 01
Choose the job
Browse ready-made kits or open an existing worker. Pick one job whose result you actually want in the mailbox, such as a daily triage digest.
- 02
Review boundaries
Check which connected apps that worker can reach, what it is allowed to write, when it runs and its per-run and monthly cost limits. A dot's app permissions do not change the worker's grants.
- 03
Run it once
Run the worker manually and read its run receipt before creating a recurring schedule or delivery. Confirm the result is useful and the cost is acceptable.
Step 2. Human
Deliver the report to your connected mailbox.
Connect a sending mailbox in WorkerKit, then add an email notification to this worker for the address connected in step 1.
- 01
Connect the sending mailbox
In WorkerKit Connected apps, connect a Google or Microsoft mailbox for sending notifications. The Email option on a worker is available only when your WorkerKit account has a connected mailbox. This sending account may differ from the mailbox your dot reads.
- 02
Add an email notification
On the selected worker, open Notifications, choose Add a notification, select Email, and enter the personal address connected to your dot under Send to. Choose when to send and what to include, then save. Keep other workers' notification settings independent.
- 03
Verify the handoff
Run the worker again. Confirm the run receipt and notification delivery status in WorkerKit, then confirm the report arrived in the mailbox your dot reads.
- 04
Ask your dot to review it
Ask the dot to find the report by sender and time, summarize the completed work, and flag any decision that needs you. Review its answer against the original report.
- Example request to your dot
Find the latest WorkerKit worker report in my connected email. Summarize what it completed, what needs my decision, and link me to the original message.
Open WorkerKit Connected apps to connect the sending mailbox before adding the notification.
The handoff runs one way. A delivered email cannot operate the fleet or answer a worker run that is waiting for input. Handle those in WorkerKit or a separately verified client.
Step 3. Human
Turn on the schedule and review the first week.
Schedule the worker only after the manual run and email delivery both succeed.
- 01
Set the cadence
Choose the worker's schedule and time zone for the job. Keep the dot's own scheduled tasks separate so you know which system initiated each result.
- 02
Watch receipts
Review early runs in WorkerKit for actual work completed, app calls and settled model cost. Adjust the worker's instruction, grants, budget or schedule if the output is noisy.
- 03
Retest any future direct connection
If a WorkerKit plugin becomes available in Dots, test its authentication and read actions before relying on writes. This email route can continue until a direct connection is verified.
Operating rules
Rules for the email handoff.
Keep OpenAI Dots and WorkerKit permissions separate, and treat the delivered message as a report.
| Rule | What it means |
|---|---|
| Treat email as delivery | A dot reads a report in a mailbox you connected. It does not gain WorkerKit fleet tools through that message, and the mail itself does not resume a worker waiting for input. |
| Keep credentials out of conversation | The email route needs no WorkerKit manager key in the dot. Do not paste one into a message, a scheduled task or the email report. |
| Keep the systems distinct | Dot Custom Rules and approvals govern dot actions. WorkerKit grants and budgets govern worker runs. Review both when the workflow crosses from one to the other. |
Quick answers
Symptoms, causes, fixes.
| Symptom | Cause and fix |
|---|---|
No dot entry point | Check your plan and region in OpenAI's current getting started guide. Enterprise beta requires an admin to enable it, and gradual rollout can take several days. |
Dot cannot find the email | Confirm the report reached the connected personal mailbox, then check the dot's Plugins connection and permissions. Ask for the report by a specific sender or date. |
Email is not available in WorkerKit | Connect a Google or Microsoft mailbox under Connected apps, then return to the worker's Notifications. The sending mailbox is an account-level connection. |
Someone asks for a WorkerKit plugin in Dots | OpenAI documents a plugin ecosystem, but this guide has not verified a WorkerKit plugin or direct MCP connection in Dots. Use the email handoff until the exact connection is tested. |
If a report does not arrive, check the WorkerKit notification and the connected mailbox before changing the assistant settings.