Pinned Tweet
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.
Overjoy gives 1,000+ CPG brands an AI sales team, working from each founder’s inbox.
Four engineers keep it running. The Nylas Email API and Hosted Authentication handle the inbox connections.
How they built it: nylas.com/case-study/overjoy…
Companies trust their AI agents less than they did in December. They’re giving them more freedom anyway. Full trust fell from 37% to 32%; no-approval autonomy nearly doubled.
We compared both waves of our survey question by question: nylas.com/blog/more-rope-few…
Can your team produce a full audit log of what your AI agents did last week, and say which agent did what? 53% of 1,030 respondents can. 37% partially. 10% can't or don't audit at all. nylas.com/agentic-ai-report-…
54% of companies had an AI agent make a mistake in the past 90 days.
We asked 1,030 people what their agents did wrong last quarter.
The State of Agentic AI: H2 2026 is out today, ungated. nylas.com/agentic-ai-report-…
The incident rate rises with scale. 45% of orgs running 1 to 5 agents reported an incident. 70% of those running more than 20.
The most common failure: an agent triggered a workflow the team had to reverse or correct (31%). A quarter had an agent update the wrong record. 18% had one send an incorrect or inappropriate email.
Last day at #TCDisrupt. Find our AE John Gray at table E12 on the 2nd floor before we pack up.
Your AI agent deserves its own inbox. Your laptop deserves the sticker.
nylas.com/disrupt
Mention OpenClaw or Hermes to a security team and the answer is usually "absolutely not."
@caleb_geene, our Director of Platform Engineering, still got Nines, our SRE agent, approved and running in production.
Here's how 🧵
Then the team tested each boundary with security in the room.
Full playbook and the approval packet template: nylas.com/blog/openclaw-herm…
The key was a one-screen approval packet:
→ Exact tools and permissions, enforced via credentials and service settings
→ Proxy + firewall blocking anything off the allowlist
→ Kill switch + spend limits outside the agent
→ Audit logs of every prompt, tool call, output
When a P1 or P2 comes in, Nines triages the ticket, tries to reproduce the bug, checks logs and metrics, posts an analysis, and opens a GitHub PR for an engineer to review.
Nylas IAM is live: give each service its own API key, limited to the permissions it needs and the accounts it works in. Every call is logged. Free on every plan.
Read how to scope an API key to one service:
nylas.com/blog/nylas-iam-sco…
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/…
Read the full write-up: nylas.com/blog/notetaker-con…
Docs:
developer.nylas.com/docs/v3/…
developer.nylas.com/docs/v3/…
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…
