Jump to section Deduplication, pause dispatch, retention windows, recording notices, and branded avatars. Set them once, change them for any customer. Today Nylas is introducing a huge update to Notetaker, with several new features and a new way to set up Notetaker. Every team that scales a meeting recording integration ends up writing the same things themselves: logic to catch duplicate bots, a way to enforce usage limitations, and retention policies to limit how long data is stored with a 3rd party. Configurations take on that work for you, and they unlock five new features too: * Deduplication. Send only one Notetaker when several people from the same organization are in the same meeting. * Custom announcements. Have Notetaker introduce itself in the meeting chat, and send reminders when late participants join. * Custom avatars. Give your Notetaker a custom image for personalized branding. * Pause dispatch. Stop sending Notetakers for a customer who has used up their recording limits, and automatically resume in the next month. * Retention. Set how long recordings are stored in Nylas, per customer. One Notetaker per meeting. Four people from the same account accept the same invite. Until now, that sent four Notetakers: four recordings of one conversation, four hours billed, and four sets of media for your app to reconcile. Turn on deduplication, and that group gets one Notetaker between them. Two different customers on the same call still get one each, since neither should end up holding the other's recording. You can switch it off further down when someone needs their own copy, so the executive whose board meeting shouldn't circulate keeps a Notetaker while everyone else is deduplicated. Customize & personalize your Notetakers. Custom announcements. Notetaker can post messages into the meeting chat when it joins and when someone arrives after it. You write the text, so it can introduce itself and follow up with a reminder that the call is being recorded. When several people arrive late in a row, a debounce window collapses them into one message instead of one per arrival, so a ten-person all-hands doesn't get ten notices. For customers selling into healthcare, financial services, and legal, an in-call recording notice is often something their compliance team requires. Custom avatars. Notetaker used to join as a blank tile with a name on it. Upload an image, and it joins showing that instead, on the one part of the integration every person in the meeting looks at. Pause dispatch when the hours run out. Applications building Notetaker functionality often set usage-based limits, so that customers don't go wild with recording too many hours. A customer on your 100-hour plan may use it up before the end of the month, leaving two weeks of meetings still booked. Now you can set dispatch_disabled_until, and Nylas stops dispatching Notetakers for that customer until that timestamp passes. Your calendar rules stay exactly as they are, so nothing needs rebuilding, and future Notetakers continue being scheduled. When the date arrives, dispatch resumes on its own and your new month's quota starts getting used. You can pause a single user, a workspace, or your whole application. Retention policies. Nylas Notetaker stores recordings and transcripts for 14 days so that your application can retrieve them. Now you set that retention period per customer, so the one whose security team asked for seven days gets seven. You can also hand it over for their control in your app: their IT admin could set a retention policy inside your settings page and your app writes it to their Configuration. How configurations work. A configuration is a saved set of defaults. You write it once, and Notetaker reads it when it's time to join a meeting. Set one for your whole application as a global default, and give your customers their own Configurations when they want something different, like a different avatar or name Nylas reads the most specific configuration available and falls back for anything you haven't set. So you can turn on recording and summaries across your app, give one customer a seven-day retention window, and give one of their teams a different display name, without any of those decisions colliding. Settings are read when the Notetaker joins, not when you schedule it. Update a configuration this afternoon and every Notetaker already booked for tomorrow joins with the new values, so changing something for a customer is one API call rather than having to iterate over everything they have scheduled. curl -request POST \ -url 'https://api.us.nylas.com/v3/notetakers/configs' \ -header 'Authorization: Bearer <NYLAS_API_KEY>' \ -header 'Content-Type: application/json' \ -data '{ "display_name": "Company defaults", "notetaker_settings": {"name": "Acme Notetaker", "recording_type": "audio_video", "transcription": true, "summary": true, "retention_time": 604800, "messages": {"on_join": [ { "type": "text", "content": "Acme Notetaker is recording and transcribing this meeting.", "send_after_ms": 3000}]}}, "deduplication_policy": "active"}' Configurations are optional. If you'd rather keep passing settings on each request, that works exactly as it does today. What teams are building with it. Sales platforms. Each account gets a recording quota. The app pauses dispatch when a customer reaches it and lifts the pause when the month turns over. Deduplication means multiple reps joining the same call only generates one recording. Applicant tracking systems. Notetaker joins under the hiring team's brand and announces itself to the candidate. Retention is set per client, so the agency handling regulated placements keeps interviews longer than the one that doesn't. Healthcare and financial software. The recording notice happens in the call and is repeated when late joiners arrive, and retention matches what each customer's compliance team signed off on, configured inside your product. Customer success tools. Deduplication keeps a five-person QBR from producing five recordings, and the custom avatar represents their brand rather than an anonymous recording bot Already building on Notetaker? One change to your requests, and it's smaller than it sounds. The top-level name and the meeting_settings object move into a single notetaker_settings object. The field names inside are identical, so it's a swap rather than a rewrite. Your webhook handling doesn't change. Legacy requests keep working while you get to it. The migration page has the before and after for every endpoint. Copy it as markdown, hand it to your coding agent, and let it do the pass. That's how Nylas migrated its own internal app, and it took less than an afternoon. Built for production. Notetaker runs on the infrastructure Nylas has been operating for more than a decade, across thousands of production applications. Nylas has completed a SOC 2 Type II examination, maintains ISO 27001 and ISO 27701 certifications, and undergoes independent HIPAA assessments. The platform's security and privacy controls help customers support their obligations under GDPR and CCPA/CPRA. Get started. Configurations and all five features are live on every Nylas application today. Create a free Sandbox account and build the whole thing before you pay for anything. Already have an account? Sign in and start with the configurations guide.

PropertyRadar powers multi-channel marketing across 160 million properties using Nylas Email API. Nylas, the communications data layer for modern software, recently published a case study detailing how PropertyRadar built the email backbone for its multi-channel marketing engine using the Nylas Email API. Hundreds of thousands of email operations a day, across Gmail, Outlook, and IMAP - through one integration. PropertyRadar powers real estate outreach at scale. PropertyRadar is the property intelligence and outreach platform used by real estate investors, agents, brokers, and marketing agencies to find, contact, and close deals with property owners across the United States. The platform covers more than 160 million properties, 250 million people, and over one billion phone numbers and email addresses. Users have completed more than $250 billion in transactions on the back of its data. Email sits at the center of PropertyRadar's value proposition: find motivated property owners before the competition, reach them with the right message at the right time, and follow up automatically so deals don't slip through the cracks. The stakes are unusually high. PropertyRadar's customers reach owners during sensitive life events like foreclosure, probate, and tax delinquency, where a deliverability misstep or provider gap can damage the trust that professionals depend on when starting those conversations. PropertyRadar's user base spans solo investors on Gmail, mortgage brokerages on Microsoft 365, and small agencies on legacy IMAP setups. Each of those providers has different authentication models, sync behaviors, and API surfaces, and provider APIs change frequently. Maintaining three separate integrations would have pulled PropertyRadar's engineering team away from what they do best: building the most accurate property data and most powerful marketing automation in the industry. PropertyRadar 5.0 increased the demand for reliable email infrastructure. The problem became urgent with the development of PropertyRadar 5.0. The March 2026 release introduced a fully integrated multi-channel marketing suite, AI-powered outreach agents, automated drip campaigns, and court-sourced distress data pulled directly from county court filings for divorce, probate, and eviction leads. Email was no longer a feature. It was a load-bearing pillar of the entire platform. Rather than staff up a dedicated email infrastructure team, PropertyRadar chose Nylas. A single Nylas integration covers Gmail, Outlook, and IMAP through one interface, along with real-time Gmail push notifications through Pub/Sub, open and engagement tracking, and webhook delivery that feeds every owner interaction back into PropertyRadar's intelligence loop. PropertyRadar's engineering team stayed focused on property intelligence while Nylas handled every layer of the email plumbing. "Email infrastructure sounds simple until you're staring down three different authentication models, two major providers that change their APIs whenever they feel like it, and a user base split across all of them," said Brian, Lead Engineer at PropertyRadar. "We made the call early: that's not our problem to solve. Nylas owns that layer, and we haven't looked back." Nylas supports hundreds of thousands of daily email operations. Today, hundreds of thousands of email operations per day flow through Nylas infrastructure on behalf of PropertyRadar users, across hundreds of connected accounts with bi-directional sync. Provider coverage mirrors PropertyRadar's user base: roughly half IMAP, over 40% Google/Gmail, and a growing Microsoft/Outlook segment. Real-time Gmail notifications through Pub/Sub mean users see lead responses instantly rather than waiting for a polling cycle. "PropertyRadar built one of the most ambitious PropTech releases we've seen this year, and the fact that they didn't have to think about email infrastructure to do it is exactly the point," said Jeff Koets, CEO of Nylas. "When email works the same way across every provider, product teams can focus on the work that actually differentiates them. That's what we're building for." AI agents expand PropertyRadar's marketing automation. PropertyRadar 5.0 introduced AI agents that help users build targeted audiences, craft marketing copy, and execute campaigns. As those agents grow more autonomous, handling outreach sequencing, follow-up timing, and lead qualification with less manual input, the demand on the underlying email infrastructure will grow with them. Nylas provides the foundation for that next chapter. To share your insights, please write to ABM at [email protected]