Connect to any inbox or calendar. The API that lets you integrate with Gmail, Microsoft, IMAP, Zoom, and 250+ mail, calendar and meeting providers in 5 minutes.
Agent Accounts is generally available today. 🚀
Your AI agent gets its own hosted email and calendar identity, provisioned with a single API call on your domain. Send, receive, and schedule, with policy enforcement and rate limits built in.
nylas.com/products/agent-acc…
ALT Agent Accounts launch card. White text on a green gradient reads: Your AI agent gets its own email and calendar. Generally available today. Nylas logo below.
Notetaker week, day 5: configurations, the piece that ties it together.
Save Notetaker settings once, apply them to every customer, override for anyone who needs something different. That's the week!
Full write-up: nylas.com/blog/notetaker-con…
Notetaker week, day 4: retention.
One customer's compliance team wants recordings gone in 7 days. Another wants 1. Set it per customer, or let their IT admin set it inside your product.
Docs: developer.nylas.com/docs/v3/…
Notetaker week, day 3: pause dispatch.
Your app already knows when a customer is out of hours. Set one date and Nylas stops sending their Notetakers, keeping future meetings scheduled, until the new month starts.
Docs: developer.nylas.com/docs/v3/…
Notetaker week, day 2: deduplication!
An eight-person meeting used to mean eight recordings. Now it's one, and the person who needs a private copy is the exception you allow.
developer.nylas.com/docs/v3/…
Notetaker week starts now! Five new features, one a day through Friday, all live today.
First up: custom announcements and custom avatars. Your bot joins with your customer's logo, introduces itself in the chat, and posts the recording notice their compliance team asked for.
The Nylas CLI treats a thread as one object. nylas email threads list --unread shows every open conversation. nylas email threads mark <id> --read clears the whole exchange in one command.
Read about how to build a conversation inbox: dev.to/mqasimca/organize-ema…
Agent Accounts give an AI trial coordinator its own mailbox and calendar. It books the site visit as its own event, so when the ethics approval slips, it moves the date once instead of sending another letter.
New post: nylas.com/blog/ai-trial-coor…
Agent Accounts gives an AI agent its own email account.
Wealthie routes adviser email through one. Clear client references file on arrival. Everything else gets inferred, scored, and queued for review below threshold.
How the scoring logic works: nylas.com/case-study/wealthi…
ALT Nylas share card on a dark green gradient. Headline: "Inbound email, filed to the right client." Below it: "Wealthie's agent scores what it can't match, and holds the rest."
Backfill a mailbox once with cursor pagination, then let message webhooks keep your copy current. Key every write on the message ID so a redelivered webhook can't duplicate a row.
Read about how to sync a mailbox into your own database:
dev.to/mqasimca/sync-a-mailb…
A support agent decides a call would be faster and sends a booking link from the address the ticket arrived on.
If they reply instead of clicking, the reply lands in the same account as the booking.
Read about how Scheduler works with Agent Accounts: nylas.com/blog/agent-account…
Agent Accounts give an AI transaction coordinator its own mailbox and calendar on the brokerage's domain.
The inspector, the lender, and the title officer all get invites from the same address, and when the closing date moves, the agent moves the appointments it organized.
Nylas CLI creates a throwaway inbox for one test run, then deletes it.
nylas agent account create e2e-$(uuidgen)@yourapp.nylas.email
Poll for the verification mail, grab the link, tear it down.
Read about how to test email flows from the terminal: cli.nylas.com/guides/e2e-ema…
GDPR does not require storing personal data in the EU. It regulates transfer, not storage location.
The EU/EEA storage requirement usually comes from a customer DPA, a public sector tender, or sector rules like DORA.
What to check before you build: nylas.com/blog/data-residenc…
The Nylas Templates API keeps email copy out of your code. Create a template once, then send with a template ID and a variables object. Change the wording later and every send picks it up, no deploy needed.
Read about how to send templated email: dev.to/mqasimca/send-templat…
Agent Accounts gives Dana Intelligence two email identities on one integration. Dana as you sends from the user's connected account. Dana as Dana sends from a dedicated address provisioned with one API call. Same code path.
Read how they built it: nylas.com/case-study/dana-in…
The Nylas Signatures API stores an HTML signature on a grant, then appends it to any send that passes its signature_id. API-sent mail doesn't inherit the user's Gmail or Outlook signature, so this is how those messages get one.
How to set one up: dev.to/mqasimca/add-email-si…
Alerts sent through an Agent Account are repliable. On-call hits reply, the message lands in the account inbox, and message.created fires your webhook. A Slack hook cannot do that.
Read about how to wire it up: dev.to/mqasimca/send-server-…
One POST to /v3/connect/custom returns a grant with a mailbox and a primary calendar. That is your AI executive assistant's identity: an address people can cc, a calendar it books on, and a message.created webhook that wakes the agent when mail lands.