Nylas

Day 3 of Notetaker week: pause dispatch, for the moment a customer runs out of hours. Picture it: a customer on your 100-hour plan burns the last hour on the 18th, with two weeks of meetings still booked. Every scheduled Notetaker is still going to join and bill. Stopping that used to mean canceling each one, turning off calendar sync, and rebuilding it all when the month rolled over. Now you set a date on a user, a workspace, or your whole application, and nothing joins, records, or bills until it passes. Scheduling never stops: Calendar Sync keeps booking Notetakers for future meetings, so when the pause lifts, everything is already in place. No canceling, no rebuilding. Two more coming at you tomorrow and Friday. Docs: https://lnkd.in/g7TeesT7

Day 2 of Notetaker week, and it's the one that's hardest to build yourself: Deduplication. Four people from the same company accept the same invite. Until now, that sent four Notetakers, four recordings of one conversation, four hours billed, and four sets of media to sort out in your app. Turn on deduplication, and that group shares one Notetaker. 👏 And it's reversible where it counts. The executive whose board meeting shouldn't circulate can keep a Notetaker of their own while everyone else is deduplicated. Three more to go this week! See the docs here: https://lnkd.in/gqsvCwMc

Notetaker just got its biggest update since launch, and we want to spend the week sharing the exciting features! 🎉 Today, we're kicking it off with the two that change how Notetaker shows up in a meeting: custom announcements and custom avatars. Announcements: write what Notetaker says when it joins and what it says when someone arrives after it. Introduce itself, follow with a recording notice, whatever your customers need. Late arrivals are debounced, so when ten people pile into a standup, they get one message instead of ten. (For customers in healthcare, financial services, or legal, that in-call notice is usually something compliance requires.) Avatars: Notetaker used to join as a blank tile with a name on it. Upload an image, and it joins showing that instead, under your brand or your customer's, on the one part of the integration every person in the meeting looks at. Stay tuned! We’re sharing one new feature a day through Friday, each with the problem it removes. If you'd rather not wait, read the full write-up now: https://lnkd.in/eKAA9q57 Docs:  https://lnkd.in/e9W9pwrM https://lnkd.in/eu59bG29

Agent Accounts give an AI trial coordinator its own mailbox and calendar, so it can book a clinical trial site visit and move it when the date slips. That matters because the visit gates patient enrollment. The investigator, the study coordinator, and the monitor have to be in the room, and today the date lives in a confirmation letter that each side copies into their own calendar by hand. When the ethics approval lands late, someone rewrites the letter and starts chasing. The agent owns the event, so it changes the date once and the invite updates everywhere. 👉 New post: https://lnkd.in/gB8sqqNg

Jo-Ann Chiam, our Chief of Customer Success, has been on the floor at apidays Toronto all morning. She's here tomorrow too! If you're building agents that need to send email or book meetings on their own, she's the person to find. A few 15-minute slots are still open: https://lnkd.in/gBPqAmYR Not at the conference, but in Toronto this week? Comment, and we'll find a time. We're hosting dinners both nights. 🍽️

Calling all Toronto residents and apidays attendees! Jo-Ann Chiam, our Chief of Customer Success, will be walking the floor tomorrow and Thursday and hosting dinners for customers while she's in town. This year, the theme is building APIs for the agentic era, which is exactly what we've focused on this year. Agent Accounts went GA in June: an AI agent gets its own inbox and calendar, so it can send email and book meetings without borrowing a human's credentials. Jo-Ann has plenty to say about what customers are building with it and what they're planning next. Grab 15 minutes with her here: https://lnkd.in/gBPqAmYR Prefer just to find her on the floor? Comment, and we'll make it happen. Same if you're in Toronto but not at the conference; we'd still love to host you for dinner.

Every email from a client’s lawyer or accountant is a compliance record. But most arrive without anything identifying which household they belong to. At Wealthie New Zealand, that meant advisers filed each thread by hand. Riki Carston, co-founder and the engineer behind the firm's software, wrote a routing layer to take it over. Emails with clear references are filed instantly. For everything else, the system infers the household, assigns a confidence score, and holds low-confidence matches for review. The agent also works from its own account, rather than an adviser’s mailbox, giving every routing decision a clear owner and audit trail. Riki built it solo, on Nylas Agent Accounts, in a single day. 👉 See how the scoring logic works: https://lnkd.in/gKa7wArk

Agent Accounts can now host a Nylas Scheduler booking page. Every Agent Account you provision comes with a calendar. Scheduler reads availability from that calendar and writes bookings back to it, so a field technician, a consultation room, a piece of equipment, or an agent your application created an hour ago can each take bookings on a page of its own. Guests on Google or Microsoft receive a full calendar invite, and their RSVP comes back to the Agent Account. When someone skips the link and emails asking about Thursday instead, that reply lands in the mailbox sitting on the same account as the booking. 👉 See how it works: https://lnkd.in/gJxAcm3a

Everyone on a real estate closing has an address. The realtor, the coordinator, the inspector, the processor at the lender, and none of them share software. The agent coordinating all of them usually doesn't. Agent Accounts gives it one: closing@yourbrokerage.com, a real mailbox and calendar provisioned through the Nylas API. So when the lender needs two more days, the email asking for the extension and the appointment it affects sits with the same identity. The agent organized that appointment, so it can move it, and the walkthrough moves with it. One email came in, and four calendars changed. 👉 New post: https://lnkd.in/g3yzPZ3u

Nylas CLI can create a throwaway inbox for a single test run and delete it when the run finishes. nylas agent account create e2e-$(uuidgen)@yourapp.nylas.email, poll it for the verification mail, pull the link out, tear it down in afterAll. That skips the Gmail catch-all, the forwarding rules, and the shared QA inbox two CI workers end up racing each other for. Accounts provision in about two seconds and accept mail immediately, so the run is not sitting on setup. ➡️ Full Playwright fixture and the GitHub Actions workflow: https://lnkd.in/gYWpfHUr