Recall AI (BYOK)
Read your Recall.ai meeting bots, recordings, transcripts metadata, calendars and calendar events with your own API key
Named email-triage methods (Inbox Zero, the 4 D's, batching) plus a decision tree for one email
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
methodology_by_namemethodology_listcompare_methodologiesmethodology_for_situationdecision_tree_referencetriage_emailcommon_mistakesresponse_templatecombining_methodologies_guideInboxzero is a fully local email-triage methodology guide that never receives or stores actual email content. methodology_by_name explains one of five named methodologies with how it works, who it's best for, and its common pitfall; methodology_list names all five, and compare_methodologies lines several up side by side. methodology_for_situation takes a described email problem and suggests the best-fitting method. decision_tree_reference shows the full triage decision tree; triage_email walks that same deterministic tree for one described email from booleans you provide (needs action, quick to handle, delegate, time-sensitive) and returns the recommended action with the path taken. common_mistakes lists frequent triage mistakes. response_template gives a short adaptable reply for a common triage moment. combining_methodologies_guide explains how these methods typically combine rather than compete. Keyless; zero upstream calls; nothing submitted is stored — and no actual email is ever read or received.
Sources: Hand-curated from widely published productivity writing on named email-management frameworks (Inbox Zero, the 4 D's, batching, priority/urgency matrices, folder systems); fully local, zero upstream calls, no email content is ever received or stored
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
9 tools, grouped by job. Every one is read-only or compute-only.
https://inboxzero.connectorbay.com/mcpRead your Recall.ai meeting bots, recordings, transcripts metadata, calendars and calendar events with your own API key
Read your Bland AI account balance, call logs with summaries and analysis, voices, inbound numbers, knowledge bases and TTS models with your own API key
Read your Postiz Cloud social media schedule: connected channels, scheduled and published posts, analytics, notifications and media library with your own API key
Read your Smartlead cold email campaigns, leads, sending accounts, warm-up stats, lead lists and overall and daily performance with your own API key
Read your Ayrshare social media post history, post details, comments, user profiles and auto-schedule times with your own API key
Read your Publer workspaces, connected social accounts, scheduled and published posts, labels and post, hashtag and best-time analytics with your own API key
"What is Inbox Zero", "explain the 4 D's", "help me triage this email", "I check email compulsively, what should I do" — a methodology guide for taming an inbox, plus a decision tree for one described email at a time. It never connects to an inbox and never reads real email — everything runs from what you tell it.
methodology_by_name explains one of five named methodologies — Inbox Zero, the 4 D's (Do/Delegate/Defer/
Delete), batching, priority-based triage, and folder/label systems — each with how it works, who it's best
for, and its most common pitfall. methodology_list names all five, and compare_methodologies lines several
up side by side. methodology_for_situation takes a described problem with your own email habits and suggests
the best-fitting methodology. decision_tree_reference shows the full triage decision tree's questions and
outcomes for reference. triage_email walks that same deterministic tree for one described email from yes/no
answers you provide — does it need action, can you handle it in two minutes, should someone else own it, is it
time-sensitive — and returns the recommended action with the path taken. common_mistakes lists frequent
email-triage mistakes with fixes. response_template gives a short, adaptable reply for a common triage
moment (delegating, declining, acknowledging and scheduling, closing a thread, setting response-time
expectations). combining_methodologies_guide explains how these methods typically combine rather than
compete — batching for when, the 4 D's for how, folders for where, priority triage for order.
Not an inbox integration, and it never receives, reads, or stores actual email content. triage_email works
entirely from the yes/no answers you supply about one message you describe — it doesn't read your inbox or
any message text.
Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Inboxzero is. Inboxzero is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated email-triage methodology reference. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.
What we receive. The arguments of each tool call — a methodology name, a described situation, a set of true/false answers about one message (for the triage tool), or a template kind — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs. Inboxzero has no mechanism to connect to an inbox or receive actual email content — no tool accepts a message body, sender address, or subject line.
Everything is answered from a bundled reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all — and no query is logged in request bodies, recorded, or used to train anything.
What we do not receive or store. We do not receive your conversation with the assistant, your email account, or any email content whatsoever, and we do not build a profile from your queries. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.
Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).
Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.
Children. Inboxzero is a general-audience service operated by the adult using the assistant.
Changes. We will post changes here with a new effective date.
Effective 25 September 2026. These terms govern use of the Inboxzero connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://inboxzero.connectorbay.com/mcphttps://inboxzero.connectorbay.com/openapi.jsonWhen you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Inbox Zero never asks for them.