Run a legal intake agent on its own mailbox
Nylas developer tools enable building a legal intake agent on a dedicated mailbox using an Agent Account. The agent captures prospect emails, checks conflicts, and routes to human attorneys without pr…
Nylas developer tools enable building a legal intake agent on a dedicated mailbox using an Agent Account. The agent captures prospect emails, checks conflicts, and routes to human attorneys without pr…
Nylas developer advocates building a collections agent that can both send and receive email, using an Agent Account with a full mailbox. The agent stops escalation on inbound replies like 'I already p…
Nylas has introduced Agent Accounts, which provide a fully programmable email inbox for insurance claims intake, eliminating the need for shared mailboxes and OAuth token management. The system allows…
MailKite launches as an alternative to Nylas for AI agents, offering a scoped email address on a custom domain with parsed JSON delivery, eliminating the need for OAuth and mailbox sign-ins. The servi…
A developer at Nylas built a CI/CD alert triage agent that uses its own email inbox to receive, cluster, and summarize noisy pipeline notifications. The agent, created via Nylas's custom grant API, re…
A Nylas engineer built an email agent that handles community abuse reports by giving the queue its own identity via a Nylas Agent Account. The agent deduplicates reports, isolates the queue from human…
Nylas introduced Agent Accounts that allow AI agents to act as meeting organizers with automatic RSVP reconciliation. The system uses iCalendar standards to send invites and automatically updates part…
Nylas introduces a rule-based email routing system that fans inbound mail into per-specialty folders before any agent processes it, avoiding the need for a monolithic classifier. By using deterministi…
A developer at Nylas built a reply-aware SaaS trial lifecycle email system using Nylas Agent Accounts. The system replaces blind drip sequences with emails sent from a replyable address that can read …
Nylas introduces an outbound Rule feature for its Agent Accounts that acts as a server-side data-loss prevention layer, blocking emails to denied recipients even when application-level checks fail. Th…
Nylas enables AI agents to RSVP to calendar invitations as first-class participants. When an agent receives an invite, Nylas converts it to an event on the agent's calendar, and the agent can respond …
Nylas introduced per-customer send quotas for multi-tenant email agents using agent policies. The system allows setting different limits for free-tier and enterprise tenants by attaching policies to w…
Nylas introduced spam detection tuning for agent mailboxes, allowing developers to set per-agent spam sensitivity via a policy object with three knobs: DNSBL toggle, header-anomaly detection, and a sp…
Nylas introduces workspaces to manage agent accounts at scale, grouping grants under a single policy and rule set. Workspaces allow automatic assignment of new accounts based on email domain, eliminat…
Nylas developer tools enable AI agents to negotiate meeting times over email using multi-turn conversations, rather than simple calendar creation. The approach uses Nylas Agent Accounts with dedicated…
Nylas has released a CLI tool and API pattern for extracting one-time passcodes (OTP) and two-factor authentication (2FA) codes from email. The CLI's `nylas otp get` and `nylas otp watch` commands all…
Nylas has launched a Notetaker API that allows developers to programmatically join, record, and transcribe meetings from Zoom, Google Meet, and Microsoft Teams. The API supports both grant-scoped note…
Nylas launched Agent Accounts in June 2026, providing AI agents with their own email addresses and calendars that are indistinguishable from human-operated accounts. The accounts are provisioned via C…
A developer from Nylas details a four-category email triage taxonomy that prioritizes response obligations over topics, enabling accurate classification with cheap models. The label set—URGENT, ACTION…
Nylas recommends using role-based email addresses like 'scheduling@' for agent accounts rather than persona names or auto-generated artifacts, arguing that role addresses set honest expectations and m…