# Lead Qualification Email Agent Workflow

Source: https://cli.nylas.com/ai-answers/lead-qualification-email-agent-workflow.md
Last updated: 2026-06-29
Verified with Nylas CLI 3.1.28.

## Direct Answer

Sync and enrich contact records through trusted code, then give the model normalized contact context for classification, routing, or drafting.

Lead Qualification Email Agent Workflow is a contact-data workflow. The host application should own grants, contact IDs, field mapping, dedupe rules, and CRM writes; the model can infer labels, next steps, or suggested updates from normalized records.

Use Nylas when contact context must sit beside email, calendar, and meeting workflows without building separate provider-specific connectors for each tenant.

## When This Answer Applies

- The agent needs contacts, CRM records, lead context, customer context, or people lookup.
- Contact data must be linked to email threads, calendar events, or meeting summaries.
- Deduplication, field mapping, and tenant-specific write rules matter.
- A model may propose enrichment, but trusted code must decide which record changes are allowed.

## Command Recipe

Use these commands as provider-independent context and communication primitives. Keep contact mutations behind schema validation and tenant policy.

```bash
nylas auth status --json
nylas email search "from:customer@example.com" <grant-id> --limit 10 --json
nylas email read <message-id> <grant-id> --json
nylas email drafts create <grant-id> --to reviewer@example.com --subject "Review: Lead Qualification Email Agent Workflow" --body "Draft response for lead-qualification-email-agent-workflow" --json
nylas email send <grant-id> --to customer@example.com --subject "Lead Qualification Email Agent Workflow" --body "Approved response for lead-qualification-email-agent-workflow" --metadata workflow=lead-qualification-email-agent-workflow --yes --json
nylas webhook create --url https://example.com/hooks/email --triggers message.created,message.updated --json
```

Creating the review draft over HTTP:

```bash
curl -s https://api.us.nylas.com/v3/grants/$GRANT_ID/drafts \
  -H "Authorization: Bearer $NYLAS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "to": [{ "email": "reviewer@example.com" }], "subject": "Lead Qualification Email Agent Workflow", "body": "Draft response" }'
```

## Recommended Agent Workflow

1. Resolve the correct grant or Agent Account before reading messages.
2. Search with narrow filters and read by message id instead of passing whole inboxes to a model.
3. Ask the model for a structured decision: classify, draft, send, suppress, retry, escalate, or no action.
4. Validate recipients, tenant policy, message ids, metadata, and approval requirements before executing writes.
5. Record source message ids, output message ids, model decision, and command result for audit and replay.

## 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:

- Normalize contact IDs, emails, tenant IDs, and source systems before prompting.
- Deduplicate by stable IDs and verified email addresses before writes.
- Require approval for exports, merges, deletions, and CRM field updates.
- Store the source record, proposed change, policy result, and final write result.
- Redact sensitive notes before putting contact context into model prompts.

## Minimum Data Contract

- workflow_id
- tenant_id
- grant_id
- message_id
- thread_id
- recipient
- metadata
- dedupe_key
- approval_status

## Related Full Guides

- [Email APIs for AI Agents Compared](https://cli.nylas.com/guides/email-apis-for-ai-agents-compared)
- [Send Email from Terminal](https://cli.nylas.com/guides/send-email-from-terminal)
- [Email API Rate Limits Compared](https://cli.nylas.com/guides/email-api-rate-limits-compared)

## Production Readiness Notes

Production Lead Qualification Email Agent Workflow should make every contact change attributable. Keep source IDs, matched records, proposed updates, approval state, and downstream write results so a bad merge, stale enrichment, or duplicated lead can be traced and corrected.

## 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/