Nylas (@nylas) / X

Nylas

7,443 posts

Nylas

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

San Francisco

Joined April 2013

Pinned
Nylas
@nylas
Jun 17
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…
Nylas
@nylas
19h
The Nylas Signatures API stores an HTML signature on a grant, then appends it to any send that passes its signature_id. API-sent mail doesn't inherit the user's Gmail or Outlook signature, so this is how those messages get one. How to set one up:
Add email signatures with the Nylas Signatures API
From dev.to
Nylas
@nylas
Jul 31
Alerts sent through an Agent Account are repliable. On-call hits reply, the message lands in the account inbox, and message.created fires your webhook. A Slack hook cannot do that. Read about how to wire it up:
Send server alerts from any box with the Nylas CLI
From dev.to
Nylas
@nylas
Jul 30
One POST to /v3/connect/custom returns a grant with a mailbox and a primary calendar. That is your AI executive assistant's identity: an address people can cc, a calendar it books on, and a message.created webhook that wakes the agent when mail lands.
Nylas
@nylas
Jul 29
An agent misclassifies an inbound email. AI-assisted: a bad draft someone catches. Autonomous: an outbound reply, a missed escalation, and a wrong CRM record before anyone sees a signal. How to govern agentic email workflows:
nylas.com
AI-Assisted vs. Autonomous Email Workflows: Architecture, Risk, and Governance | Nylas
AI-assisted email workflows wait for human review before acting. Autonomous agents execute across connected systems without it. Learn the architectural and governance differences — and how to build...