Nylas

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.

[Nylas @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.

https://t.co/TzW225Kw1U

[Nylas @nylas]

You can’t predict what an agent will decide. You can set what it’s able to reach. With Nylas IAM, a read-only key for one mailbox means a send attempt returns 403 and lands in Access Activity. https://t.co/7bnWxbDHyn

[Nylas @nylas]

Want time with someone from our DevRel, sales, or CS teams? Send us a message, and we’ll book a meeting before the show: https://t.co/U02WSFpQGt

See you in Lisbon 👋

[Nylas @nylas]

Nylas is heading to @WebSummit in Lisbon, Nov 9–12 🇵🇹

Find us at Booth E493, Pavilion 4. Tell us what you’re building, whether that’s email and calendar in your product or an inbox for your AI agents.

Stop by to enter our Bose QuietComfort headphones giveaway 🎧

[Nylas @nylas]

58% of teams with customer-facing AI agents let them email customers as an employee at least some of the time. When the agent gets it wrong, the customer blames that employee and the audit log shows their name.

New data from our H2 2026 survey: https://t.co/JoDER6JykK

[Nylas @nylas]

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: https://t.co/oalaRiJD7G

[Nylas @nylas]

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: https://t.co/GvDPPgfznF

[Nylas @nylas]

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. https://t.co/mBI4QW3YGK

[Nylas @nylas]

When something does go wrong, nearly half of teams cannot say which agent did it. Only 53% can produce a full audit log of what their agents did last week.

[Nylas @nylas]

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. https://t.co/mBI4QW3YGK

[Nylas @nylas]

The incident rate rises with scale. 45% of orgs running 1 to 5 agents reported an incident. 70% of those running more than 20.

[Nylas @nylas]

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.

[Nylas @nylas]

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.

https://t.co/WxwNW52ewg

[Nylas @nylas]

Then the team tested each boundary with security in the room.

Full playbook and the approval packet template: https://t.co/f067HD3qvb

[Nylas @nylas]

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 🧵

[Nylas @nylas]

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

[Nylas @nylas]

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 @nylas]

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:
https://t.co/SY2pCodJMw

[Nylas @nylas]

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: https://t.co/xxG8d9Pxg6

[Nylas @nylas]

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: https://t.co/1aymhrP0Co

[Nylas @nylas]

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: https://t.co/iLCqtueSkj