What is Gork mail (also searched as Grokmail or gork.email)?

Gork mail (gork.email, often spelled Grokmail or Grok mail) is programmable email infrastructure designed specifically for AI agents, LLMs, and autonomous workflows. It provides real email addresses, API & MCP access, signed webhooks, and deliverability guardrails.

How does Gork mail work for AI agents?

Gork mail gives each AI agent its own isolated email address via one API call or MCP tool. Agents can send emails, receive inbound messages via signed webhooks, search conversation history, and manage threads.

Can I use Gork mail with Claude Code, Cursor, or LangChain?

Yes. Gork mail ships a native Model Context Protocol (MCP) server. Running npx -y -p @gork/sdk gork-mcp gives Claude, Cursor, Goose, or Windsurf 13 native email tools.

Back to all blueprints

Templates · Productivity / Autonomous Executive Assistant

AI Scheduling Agent (Meetings & Calendars)

Your agent coordinates dates, parses timezones, and handles counter-proposals — Gork keeps every offer threaded.

Create handle All blueprints

Operational Bottleneck

Scheduling software like Calendly forces humans to click links. Executive clients and enterprise partners expect human-like email dialogue. Traditional LLM integrations get confused by multi-party timezone arithmetic.

Agents lose track of which time slots were already offered, creating double-booking conflicts when multiple counterparties reply asynchronously.

Gork Infrastructure Layer

Structured <90ms Delivery

Gork provides atomic thread tracking so scheduling agents can tie each proposed slot to specific email thread IDs and calendar hold states.

Execution Artifacts

System prompt, SDK code & webhooks

Copy the system prompt directly into your model context (Claude, ChatGPT, or custom orchestrator).

system-prompt.txt

1You are an AI Executive Scheduling Assistant for Elena Vance (VP of Product).
2Your goal is to coordinate executive meetings via email with clients, candidates, and partners.
3
4RULES:
51. Available Window: Monday through Thursday, 1:00 PM to 5:00 PM US Eastern Time (ET).
62. Timezone Precision: Always convert your host's availability into the client's local timezone. State both timezones clearly: e.g. "2:00 PM ET (11:00 AM PT)".
73. Offer Constraints: Offer exactly 3 distinct options across 2 different days.
84. Confirmation Trigger: When the counterparty selects an option (e.g. "Tuesday at 2 works"), parse the exact timestamp, verify availability via calendar API, and generate calendar invite details.
9
10OUTPUT SCHEMA:
11{
12  "status": "proposing_options" | "confirming_slot" | "conflict_reschedule",
13  "chosenTimeUtc": string | null,
14  "replyBody": string
15}

Autonomous Lifecycle

PHASE 01

Client Suggests Times

Email received proposing or requesting available meeting windows.

PHASE 02

Calendar Slot Evaluation

Agent cross-references host calendar API and timezone offsets.

PHASE 03

Draft Negotiation

Agent sends 3 distinct choices or confirms selected slot in-thread.

PHASE 04

Calendar Invite Sent

Your integration generates the ICS invite from the agreed slot and sends it — Gork holds the thread it was agreed in.

Give your agents programmable email identities.

Provision handles on demand under your own domain. Inbound email never counts against your plan.

Create handle Compare plans

Related Agent Blueprints

Support & Ops

AI Support Agent (Triage, Threading & Escalation)

Receives customer tickets, maintains multi-turn conversation threads, and escalates emergencies.

View blueprint →

Sales & Growth

AI Sales / SDR Agent (Outreach & Objection Handling)

Sends targeted outreach, understands prospect replies, qualifies intent, and books demos.

View blueprint →

Enterprise Ops

AI Procurement Agent (RFQ Quotes & Vendor POs)

Your agent requests quotes, reads pricing tables from replies, and follows up on purchase orders — Gork threads it all.

View blueprint →