Menu
Mattering Automations connector

A Nylas MCP built for email automation and calendar workflows

Connect one Nylas API key and the mailboxes, calendars, and contact books behind your Nylas grants become workflow steps. An AI agent can triage an inbox into tasks, a scheduling workflow can find a slot every participant is free for and book it, and outbound email can wait in a draft until a person approves the send.

45 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Nylas MCP connector does

The Nylas connector for Mattering Automations is 45 nodes across the Nylas v3 email, calendar, and contacts API: messages and threads with provider-native search, the full draft lifecycle from compose to send, folders and labels, attachment metadata and downloads, calendars and events with RSVP, availability and free/busy scheduling lookups, contacts and contact groups, application webhooks for real-time notifications, and the grants that name which connected account each call touches. One API key plus its region authenticates all of it.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can search a mailbox, read the full body of a message, check who has answered an event invitation, and compose a reply as a draft for a person to approve, without anyone opening a mail client.

Nylas publishes its own official MCP server, hosted at regional endpoints and covering email, calendar, contacts, and its Notetaker product, and if all you want is an assistant with a direct line to Nylas it is a genuine option. This connector is for the workflows where Nylas is one step among many: on the Mattering canvas the same nodes sit next to every other connector and the platform itself, so an arriving message can open a task with the attachment saved beside it, a booking can be written into a Mattering database, and a drafted reply can wait behind a human approval step. Use whichever fits, or both.

The safety modeling is stated plainly. Of the 45 nodes, 20 read and 25 act, and 11 are flagged destructive. Eight of those are deletes, and the other three delete nothing at all: Nylas: Send Message, Nylas: Send Draft, and Nylas: Send Event RSVP are destructive-classed because they deliver real email from the connected account, and a sent email cannot be recalled. The connector's designed-for pattern is drafted-for-approval: Nylas: Create Draft composes without sending, a person reviews, and only then does Nylas: Send Draft fire. Some surfaces are deliberately not shipped: the separate Nylas Scheduler product, account connection flows, scheduled-send management, and Smart Compose stay off the canvas.

One connection, three surfaces

  • Visual automations. Drag Nylas nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Nylas node, ready to drop on the canvas

45 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 20

Nylas: Download Attachment

Download an attachment's file content, returned base64-encoded at data.file_base64 with its content type and size. Files over the 5 MB (base64) cap fail with a clear error - check size first with Nylas: Get Attachment Metadata.

Nylas: Get Application

Fetch the Nylas application the API key belongs to: application ID, region, environment, and branding. Grant-independent, so it works before any account is connected - the credential health check to run first in any Nylas automation.

Nylas: Get Attachment Metadata

Fetch an attachment's metadata - filename, content type, and size - without downloading the bytes. Check the size here before Nylas: Download Attachment (5 MB node cap).

Nylas: Get Availability

Find open meeting slots across one or more connected accounts: returns time_slots where every listed participant is free for the requested duration. GRANT-INDEPENDENT path - participants are named by email in the body (each must belong to a grant on this application). A read: it books nothing; feed a chosen slot into Nylas: Create Event.

Nylas: Get Event

Fetch one event: time, participants and their RSVP statuses, conferencing details, and recurrence. The participant check to run before Nylas: Send RSVP.

Nylas: Get Free/Busy

Fetch busy time blocks for up to 50 email addresses (Google; 20 on Microsoft) as seen from the connected account's provider - colleagues on the same domain included, no extra grants needed. Returns per-email time_slots with status busy; gaps are free.

Nylas: Get Grant

Fetch one grant: the connected account's email, provider, scopes, and valid/invalid status. The status check to run before a long email or calendar automation.

Nylas: Get Message

Fetch one message with its full body, participants, folders, and attachment metadata (attachment IDs feed the attachment nodes).

Nylas: Get Thread

Fetch one thread: participants, message IDs (feed Nylas: Get Message for bodies), folders, and state.

Nylas: List Calendars

List the account's calendars with IDs, names, timezones, and read-only/primary flags. The calendar ID from here is required by every event node.

Nylas: List Connectors

List the auth connectors (providers) configured on the application - google, microsoft, imap, virtual_calendar - with their scopes. Tells an automation which account types this application can connect.

Nylas: List Contact Groups

List the account's contact groups (Google labels, Microsoft folders) with IDs and names - the values the contact group filter and the groups field take.

Nylas: List Contacts

List the account's contacts with names, emails, phone numbers, and groups. Filter by email, phone, source (address_book, inbox, domain), or contact group.

Nylas: List Drafts

List the account's email drafts with their draft IDs, which the update, send, and delete nodes need. Documented filters (subject, any_email, thread_id, unread, starred, has_attachment) are reachable via Extra query parameters.

Nylas: List Events

List events on a calendar, filtered by time range, title, attendee, or busy state. start/end are range FILTERS on the entity listing (Unix seconds), not a reporting window. calendar_id is required by the API.

Nylas: List Folders

List the mailbox's folders (Gmail labels, Microsoft/IMAP folders) with IDs, names, and unread/total counts. Folder IDs feed the message/thread folder filters and moves.

Nylas: List Grants

List the connected accounts (grants) on the application with their grant IDs, emails, providers, and valid/invalid status. Nearly every other Nylas node needs a grant ID from here. Paginates with limit/offset (not page_token).

Nylas: List Messages

List messages in the connected mailbox, newest first, with filters on sender, recipient, folder, read/starred state, received-time range, and provider-native search. List responses carry a snippet; use Nylas: Get Message for the full body.

Nylas: List Threads

List conversation threads with participants, snippet, message IDs, and unread/starred state - the one-row-per-conversation view of the mailbox.

Nylas: List Webhooks

List the application's webhook destinations with their IDs, URLs, trigger types, and active/failing status.

Action nodes 25

Nylas: Create Calendar

Create a calendar on the connected account. Reversible with Nylas: Delete Calendar. Microsoft accepts only the name at creation; the other fields apply to Google and virtual calendars.

Nylas: Create Contact

Create a contact in the connected account's address book. Reversible with Nylas: Delete Contact.

Nylas: Create Draft

Create an email draft in the connected account. Nothing is sent - the draft sits in the mailbox for review until Nylas: Send Draft fires it or a human sends it from their mail client. Reversible with Nylas: Delete Draft. The draft-for-approval pattern is the safe way to automate outbound email.

Nylas: Create Event

Create a calendar event. Reversible with Nylas: Delete Event - BUT with notify_participants true the provider emails invitations to every participant, and those emails cannot be recalled; leave it false in test runs. The 'when' object sets the time in one of four documented shapes.

Nylas: Create Folder

Create a folder (or Gmail label) in the mailbox. Reversible with Nylas: Delete Folder. Colors apply to Google only.

Nylas: Create Webhook

Create a webhook destination for real-time notifications (message.created, grant.expired, event.created, ...). Nylas immediately sends a challenge GET the endpoint must echo within 10 seconds, or creation fails. The response's webhook_secret is shown ONCE - store it to verify signatures. Reversible with Nylas: Delete Webhook.

Nylas: Delete Calendar

DESTRUCTIVE: delete a calendar and EVERY event on it, permanently. Primary calendars cannot be deleted. Export or read the events first if there is any doubt.

Nylas: Delete Contact

DESTRUCTIVE: delete a contact from the account's address book. Its details are gone unless read beforehand.

Nylas: Delete Draft

DESTRUCTIVE: delete a draft. Its composed content is gone unless read beforehand (Nylas: List Drafts). Nothing is sent or recalled by this.

Nylas: Delete Event

DESTRUCTIVE: delete an event from the calendar. Its details are gone unless read beforehand, and with notify_participants true the provider emails cancellations to participants.

Nylas: Delete Folder

DESTRUCTIVE: delete a folder. Provider behavior varies: Gmail removes the label from its messages (messages survive), while folder-based providers can delete or orphan the contents. Check the folder's total_count first.

Nylas: Delete Grant

DESTRUCTIVE: revoke a grant, disconnecting the account from Nylas. Every node using this grant ID starts failing immediately, and reconnecting requires the end user to authenticate again. The mailbox itself is untouched.

Nylas: Delete Message

DESTRUCTIVE: delete a message from the mailbox. Provider behavior varies (some trash, some remove permanently) - prefer Nylas: Update Message with a Trash folder move when recoverability matters.

Nylas: Delete Webhook

DESTRUCTIVE: delete a webhook destination. Notifications to it stop immediately, and its signing secret cannot be recovered.

Nylas: Send Draft

DESTRUCTIVE: send an existing draft to its recipients. A SENT EMAIL CANNOT BE RECALLED, so this node must never run in a blind test matrix - read the draft's recipients and body upstream first. (POST to the draft's own path sends it; there is no /send suffix in Nylas v3.)

Nylas: Send Event RSVP

DESTRUCTIVE: RSVP to an event as the connected account - yes, no, or maybe. This SENDS A REAL REPLY EMAIL to the event's organizer, which cannot be recalled, so it must never run in a blind test matrix. The status itself can be changed by RSVPing again.

Nylas: Send Message

DESTRUCTIVE: send an email from the connected account, immediately or scheduled via send_at. A SENT EMAIL CANNOT BE RECALLED, so this node must never run in a blind test matrix - verify recipients upstream. Fill reply_to_message_id to reply on an existing thread with correct headers. Sending is synchronous and can take up to ~2 minutes on slow providers.

Nylas: Update Calendar

Update a calendar's name, description, timezone, or color. Only the fields you fill are sent. Microsoft allows updating only the name.

Nylas: Update Contact

Update a contact. Only the fields you fill are sent, but note array fields (emails, phone_numbers) REPLACE the stored array wholesale - read the contact first and send the full merged list.

Nylas: Update Draft

Update an existing draft's content or recipients. Only the fields you fill are sent; nothing is delivered until the draft is sent.

Nylas: Update Event

Update an event's time, title, participants, or details. Only the fields you fill are sent. With notify_participants true the provider emails updates to participants (unrecallable); leave it false in test runs.

Nylas: Update Folder

Rename a folder, re-parent it, or (Google) change its label colors. Messages inside are untouched.

Nylas: Update Message

Update a message's flags: mark read/unread, star/unstar, or move it between folders. Only the fields you fill are sent, and every change is reversible by writing the previous value back.

Nylas: Update Thread

Update a whole thread's flags in one call: mark every message read/unread, star/unstar, or refile the thread. Reversible by writing the previous value back.

Nylas: Update Webhook

Update a webhook destination's URL, triggers, or alert emails. Changing the URL re-runs the challenge check.

Connecting Nylas takes one credential

Nylas authenticates API requests with an API key sent as a Bearer header. Keys are created per application in the Nylas Dashboard on the API Keys page, they are displayed once at creation, and they carry an expiration you choose. Nylas v3 runs isolated regions with separate hosts for the US and EU, and a key only works against the region its application lives in, so the Mattering credential stores both the key and the region. Data access is per grant: a grant is one connected end-user account (Google, Microsoft, IMAP, or virtual calendar) authorized through Nylas hosted authentication, and nearly every node takes a grant ID naming whose mailbox or calendar it touches.

1

Sign in to the Nylas Dashboard, open your application, and note its region (US or EU). Click API Keys in the left navigation, click Generate new key, name it, choose an expiration, and click Generate key.

2

Copy the key when it is shown. The Dashboard displays an API key secret once; if you lose it, you generate a new key.

3

In Mattering Automations, open Connectors, click Add Connector, choose Nylas, and create a credential with the API key and the region that matches your application.

4

Click Test Connection. Mattering calls the Nylas applications endpoint, which works before any account is connected: a success returns your application ID and region, and an error means the key is wrong, expired, or pointed at the wrong region.

5

All 45 Nylas nodes appear in the canvas palette. Run Nylas: List Grants first: it returns the connected accounts with their grant IDs, and nearly every other node needs one.

Common uses for the Nylas MCP

Outbound email with a human approval gate

The safe way to automate email is to separate composing from sending. Nylas: Create Draft writes a reply or a fresh message into the connected mailbox without delivering anything, the workflow opens an approval task with the draft's recipients and body attached, and only after a person signs off does Nylas: Send Draft deliver it. For sends that skip the gate, Nylas: Send Message delivers immediately or on a schedule via send_at, which Nylas accepts from 1 minute to 30 days in the future. Both send nodes are flagged destructive because a sent email cannot be recalled.

An inbox that files itself

Nylas: List Messages filters the mailbox by sender, recipient, folder, read state, received-time range, and provider-native search, and Nylas: Get Message returns the full body with attachment metadata. A triage workflow can open a Mattering task for each message that matches, write the details into a database, then use Nylas: Update Message to mark it read, star it, or move it to a processed folder, all reversible by writing the previous value back. Nylas: Update Thread does the same for a whole conversation in one call.

Scheduling without the back-and-forth

Nylas: Get Availability takes a list of participants by email, each connected as a grant on your application, and returns the time slots where every one of them is free for the requested duration. It books nothing, so the workflow chooses a slot and feeds it into Nylas: Create Event. Nylas: Get Free/Busy answers the narrower question, returning busy blocks for up to 50 email addresses on Google or 20 on Microsoft as seen from the connected account's provider, including colleagues on the same domain who never connected a grant.

Calendar upkeep an agent can hold

Nylas: List Calendars returns the calendar IDs every event node needs, Nylas: List Events filters a calendar by time range, title, or attendee, and Nylas: Get Event shows each participant's RSVP status. From there an agent can create, update, or RSVP to events. One flag matters more than the rest: notify_participants makes the provider email invitations, updates, or cancellations to every participant, and those emails cannot be recalled, so leave it false in test runs and turn it on deliberately.

Contacts synced with the rest of your work

Nylas: List Contacts pulls the address book with names, emails, phone numbers, and groups, filterable by email, source, or contact group, and a scheduled sweep can mirror it into a Mattering database next to your deals and tasks. Writes go the other way: Nylas: Create Contact and Nylas: Update Contact push changes back. One documented sharp edge the node description repeats: array fields like emails and phone numbers replace the stored array wholesale, so read the contact first and send the full merged list.

Real-time email and calendar triggers

Nylas: Create Webhook registers a destination URL for events like message.created, event.created, or grant.expired, and pointing it at a Mattering inbound webhook trigger turns those into workflow starts. Nylas immediately sends a challenge request the endpoint must answer within 10 seconds, and the response includes a signing secret shown once, used to verify each delivery's signature. Nylas: List Webhooks shows every destination with its active or failing status, so a health sweep can catch a dead webhook before you miss a week of events.

Example: A message arrives: file it, draft the reply, send only after a person approves

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a Nylas webhook for message.created delivers to a Mattering inbound webhook trigger the moment mail lands in the connected inbox.

2

Nylas: Get Message fetches the full body, participants, and attachment metadata for the new message.

3

Nylas: Get Attachment Metadata checks each attachment's size, and Nylas: Download Attachment pulls files under the 5 MB node cap into the run.

4

The workflow writes the message details into a Mattering database and opens a task in Mattering Productivity with the attachment saved beside it.

5

Nylas: Create Draft composes a reply on the same thread. Nothing is sent; the draft sits in the mailbox for review.

6

A person approves the task, and Nylas: Send Draft delivers the reply. Nylas: Update Message then marks the original read and moves it to a processed folder.

Nylas MCP questions, answered

What Nylas operations are supported?

45 nodes on the Nylas v3 API: 20 query nodes and 25 action nodes covering messages (list, get, update flags, send, delete), threads, the full draft lifecycle (list, create, update, send, delete), folders and labels, attachment metadata and downloads, calendars, events with create, update, delete, and RSVP, availability and free/busy lookups, contacts and contact groups, application webhooks, and grant management. Deliberately not shipped: the separate Nylas Scheduler product, account connection and OAuth flows, scheduled-send management, Smart Compose, attachment upload sessions, and whole-thread delete.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Nylas publishes an official MCP server. Why use this connector?

Nylas does host its own MCP server, covering email, calendar, contacts, and its Notetaker product, and if you want an assistant talking to Nylas alone it is a genuine option. This connector earns its place when Nylas is one step in a larger workflow: the same canvas holds your other connectors and the Mattering platform itself, so an arriving message can open a task, a drafted reply can wait behind a human approval step, and a booking can land in a Mattering database next to the rest of your work. Credentials live in one place with your other connector secrets, and the same nodes serve visual automations and AI agents alike.

Do I need a paid Nylas plan?

Nylas is a commercial API: production pricing is per connected account, on plans published at nylas.com/pricing. For development, Nylas offers a Sandbox environment you can build against before moving to a paid plan, and a single connected account is enough to exercise the full email, calendar, and contacts surface. One testing caution that has nothing to do with pricing: sends from a connected account deliver real email, so test sends only to addresses you own.

Can an AI agent send email safely?

The guardrails are modeled into the nodes rather than implied. Nylas: Send Message, Nylas: Send Draft, and Nylas: Send Event RSVP are all flagged destructive, not because they delete anything but because a sent email cannot be recalled, so workflows gate them the way they gate deletes. The designed-for pattern is drafted-for-approval: Nylas: Create Draft composes without sending, a person reviews the recipients and body, and Nylas: Send Draft fires only after sign-off. Sending is synchronous and Nylas documents that slow providers can take up to about two minutes, so the send nodes carry extended timeouts.

What is a grant, and why does almost every node ask for a grant ID?

A grant is one connected end-user account: a Google, Microsoft, or IMAP mailbox, or a virtual calendar, authorized through Nylas hosted authentication. The API key authenticates the request, and the grant ID names whose data it touches, which is how one credential can serve many mailboxes. Nylas: List Grants returns the connected accounts with their IDs, providers, and valid or invalid status, and the grant pickers across the connector are populated from it. Nylas: Delete Grant is flagged destructive because it revokes the connection: every node using that grant starts failing, and reconnecting requires the end user to authenticate again.

Can workflows read and save email attachments?

Yes, in two steps. Nylas: Get Attachment Metadata returns an attachment's filename, content type, and size without downloading anything, and Nylas: Download Attachment returns the file content base64-encoded, capped at 5 MB per download, with larger files failing on a clear error rather than truncating. Attachment IDs ride on the message object from Nylas: Get Message, and both attachment nodes also require the message ID, because Nylas scopes attachment IDs to their message. Check the size with the metadata node before downloading.

What is deliberately not included?

Several surfaces, each for a stated reason. The Nylas Scheduler product has its own session-based auth model, and the availability, free/busy, and event nodes already cover scheduling automations, so it stays separate. Connecting accounts is an interactive hosted-auth flow, not a canvas action, so grant creation is out. Whole-thread delete exists upstream but trashes every message in the conversation at once, so the finer-grained message delete and thread refile shipped instead. Scheduled-send management, Smart Compose, and attachment upload sessions are out of this cut, and Microsoft attachments over 25 MB need Nylas's large-attachments flow, which the send nodes note rather than half-support.

45 nodes waiting on the canvas

Put Nylas to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Nylas is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products