Nylas

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…

Lighthouse is an all-in-one platform for VC investors. Sourcing, CRM, LinkedIn outreach, email, scheduling, workflows. Three founders built it. With a coding agent. The one part they didn't build: the communications layer. That's Nylas. nylas.com/case-study/lig…

Your free-trial user and your enterprise customer are running into the exact same daily send cap. One of them shouldn't be. Read about how to set per-tier caps with Agent Account policies: dev.to/mqasimca/set-p…

Agent Accounts gives your AI sales agent its own inbox AND its own calendar. So when the prospect writes back "sure, next week?" the agent checks availability, books the meeting, and sends the invite. No handoff, no second system to keep in sync. nylas.com/blog/ai-sales-…

PropertyRadar covers 160M properties. Reaching users means email across Gmail, Outlook, and IMAP. Three auth models, three APIs, one maintenance burden they no longer own. One Nylas integration. Hundreds of thousands of messages a day. nylas.com/case-study/pro…

Your agent got added to the standup. It didn't ask to be there. But it can at least click "Maybe" like a professional. Read about how to make Agent Accounts RSVP like real invitees: dev.to/mqasimca/let-y…

Inbound Rules on Agent Accounts match the sender, not the subject. That trips up basically everyone. @mqasimcax on what Rules can and can't do, and where subject filing actually belongs: dev.to/mqasimca/auto-…

Full post 👇 nylas.com/blog/enterpris…

So we broke AI security into 4 governance problems: permissions authentication monitoring vendor risk Plus a risk-tiering framework to classify any AI comms workflow before it ships: read-only → read-write → autonomous.

Most enterprise AI security conversations start with the model. That's the wrong starting point. Just as much risk lives in the workflow around the model, not the model itself.

An agent BCCs a competitor’s domain. Your allowlist never sees it because it only checked To. Nylas outbound Rules inspect To, CC, BCC, and the SMTP envelope at send time, blocking risky messages before they leave the building. Set it up here: dev.to/mqasimca/stop-…

@intentionally Hey @intentionally , followed up internally & someone will reach out with you shortly!

@nylas I'm trying to get set up with Nylas (signed the agreement already) and I can't get ahold of my sales rep on next steps, and can't find a place to get technical support. Can anyone help?

Email threads suck because they're always displayed linearly. I built something to visualize them better. threads.barraclough.nz uses the @nylas Threads API to visualize your emails, making it easy to see how threads twist & turn & become complex messes.

Under a day. That's how long it took Wealthie to build a working agent inbox on Nylas Agent Accounts. Co-founder Riki Carston built a routing layer that reads each client email and files it to the right household on its own. Solo, on one API. nylas.com/case-study/wea…

Developers are already building on it. Dana Intelligence built every user a dedicated assistant with its own inbox. Kevin Chan is running a one-person eng team on Agent Accounts, replacing 20+ internal SaaS tools. See what you can build. nylas.com/blog/introduci…

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…

@BrendanEich @kenn @peer_rich @BrendanEich @kenn @peer_rich Clarifying: Nylas wasn't breached, no credentials leaked. An attacker abused our developer sandbox to run consent phishing. We shut it down immediately & are tightening our controls. Production customers always use their own OAuth client.

@kenn @peer_rich @nylas s/credential/client secret/, sorry. Grok helped me out, hope it didn't fib or hallucinate. It sounds right but I have not had time to research and double-check everything: x.com/i/grok/share/3…

OAuth scams are becoming more and more popular this time a malicious @nylas OAuth client is being used to attack one of our employees (who immediately understood its a scam and has reported it) the playbook is simple: 1. obtain a Google OAuth client 2. pretend to send a .docx 3. immediately open the Google OAuth splash screen 4. Attacker gains full access to Email, Calendar and more officially it falls under phishing, however attackers no longer make fake login forms but instead show official google log in screens most people fall for it because they check the website, see google.⁠com AND nylas.⁠com (which is also legit) and think its safe. signing into google to view a document is also very common

@peer_rich Thanks Peer for reporting this via our official abuse channel. We take abuse reports seriously and act quickly. We reviewed the report and invalidated the associated client IDs, and reported the site to Vercel. We appreciate your vigilance and sharing our response publicly.