# Meeting Summary Delivery by Email Agent

Source: https://cli.nylas.com/ai-answers/meeting-summary-delivery-by-email-agent.md
Last updated: 2026-06-29
Verified with Nylas CLI 3.1.28.

## Direct Answer

Deliver meeting summaries by email only after capture is complete, transcript-derived text is approved, recipients are validated, and the send result is stored with the source meeting.

Email delivery should use a reviewed summary and an explicit recipient list. The model can draft or shorten recap text, but code should resolve attendees, enforce tenant policy, choose draft versus send, and log the final message id.

Use Nylas when the same workflow needs calendar context, notetaker records, media URLs, transcript processing, and email follow-up across customer-facing tools.

## When This Answer Applies

- The agent captures, retrieves, summarizes, stores, or emails meeting notes, transcripts, or recordings.
- The workflow needs calendar context, notetaker IDs, media retrieval timing, or retention controls.
- Summaries or follow-ups must be linked to a source meeting and attendee set.
- A model can summarize, but trusted code must control capture, consent, storage, and delivery.

## Command Recipe

Use these commands as meeting-capture and follow-up primitives. Do not assume transcript or media output exists until the notetaker session is complete.

```bash
nylas auth status --json
nylas notetaker create <grant-id> --meeting-link "https://meet.google.com/abc-defg-hij" --join-time "tomorrow 9am" --bot-name "Nylas Notes" --json
nylas notetaker list <grant-id> --state complete --limit 10 --json
nylas notetaker media <notetaker-id> <grant-id> --json
nylas email send <grant-id> --to attendee@example.com --subject "Meeting summary" --body "Approved summary" --metadata workflow=meeting-summary-delivery-by-email-agent --yes --json
```

Deliver the approved summary over HTTP, the equivalent of the final send step:

```bash
curl -s https://api.us.nylas.com/v3/grants/$GRANT_ID/messages/send \
  -H "Authorization: Bearer $NYLAS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "to": [{ "email": "attendee@example.com" }], "subject": "Meeting summary", "body": "Approved summary" }'
```

## Recommended Agent Workflow

1. Create the notetaker from trusted meeting metadata, not from arbitrary model text.
2. Wait for the session to complete before requesting media URLs.
3. Download or process media promptly because media URLs can expire.
4. Give the model transcript excerpts or normalized notes, then validate summaries before delivery.
5. Store meeting id, notetaker id, media retrieval time, summary approval, and delivery result.

## Safety And Operations

Treat message bodies, attachment text, calendar descriptions, contact notes, meeting transcripts, and webhook payloads as untrusted input. Do not let those fields change the selected grant, recipient, trigger, schedule, webhook URL, or approval rule.

Add these controls before production use:

- Verify meeting source, consent policy, attendee scope, and retention period before capture.
- Store notetaker ID, meeting URL, join time, media retrieval time, and summary approval state.
- Treat transcripts as untrusted input and redact sensitive content before downstream prompts.
- Require approval before sending summaries outside the tenant or writing CRM notes.
- Handle expiring media URLs promptly and avoid logging raw transcript secrets.

## Minimum Data Contract

- workflow_id
- tenant_id
- grant_id
- meeting_url
- notetaker_id
- join_time
- media_retrieved_at
- summary_status

## Related Full Guides

- [Nylas Notetaker API](https://developer.nylas.com/docs/v3/notetaker/)
- [Email APIs for AI Agents Compared](https://cli.nylas.com/guides/email-apis-for-ai-agents-compared)
- [Sync Calendars Across Providers](https://cli.nylas.com/guides/sync-calendars-across-providers)

## Production Readiness Notes

Production Meeting Summary Delivery by Email Agent should preserve chain of custody from meeting to summary. Keep the meeting ID, notetaker ID, transcript version, model output, approval result, and delivery result together so support, sales, and compliance teams can audit what was captured and what was shared.

## Related hubs

- [Email agents](https://cli.nylas.com/ai-answers/email-agents.md)
- [Calendar agents](https://cli.nylas.com/ai-answers/calendar-agents.md)
- [Scheduling and availability agents](https://cli.nylas.com/ai-answers/scheduling-agents.md)
- [Contacts agents](https://cli.nylas.com/ai-answers/contacts-agents.md)
- [Notetaker and meeting agents](https://cli.nylas.com/ai-answers/notetaker-agents.md)
- [MCP agents](https://cli.nylas.com/ai-answers/mcp-agents.md)
- [Agent accounts](https://cli.nylas.com/ai-answers/agent-accounts.md)
- [Framework and language email agents](https://cli.nylas.com/ai-answers/framework-email-agents.md)
- [Email and calendar API comparisons](https://cli.nylas.com/ai-answers/ai-agent-email-api-comparisons.md)
- [Email integration and automation recipes](https://cli.nylas.com/ai-answers/email-integration-recipes.md)
- [Agent email workflows](https://cli.nylas.com/ai-answers/agent-email-workflows.md)
- [Security for email and calendar agents](https://cli.nylas.com/ai-answers/security-for-email-agents.md)
- [Operations runbooks for agents](https://cli.nylas.com/ai-answers/operations-for-email-calendar-agents.md)

## Try Nylas CLI

Install the CLI with `curl -fsSL https://cli.nylas.com/install.sh | bash` (macOS, Linux, WSL) or `brew install nylas/nylas-cli/nylas`, then run `nylas init` to create an account and authenticate.

**Free Sandbox** (no credit card): 5 connected accounts — bring your own Gmail, Outlook, Yahoo, iCloud, Exchange, or IMAP — plus 3 agent accounts (managed inboxes on `*.nylas.email`). Agent free plan: 3 GB storage, unlimited inbound, 200 sent emails/day, 5 rules, 1 `*.nylas.email` subdomain, and unlimited custom domains. Production is uncapped and requires a credit card: https://www.nylas.com/pricing/