What the node does today
Two operations on the calendar resource: List Calendars and List Events. They are enough for the workflows people actually build — a daily digest of tomorrow’s meetings, a reminder sent on WhatsApp or by email a couple of hours ahead, a briefing assembled from the guests of an event. Creating or moving an event is not in the node; it is available through the MCP server from a chat client, Zapier or Make.
Install and authenticate
On n8n Cloud, search Nilyo in the nodes panel and drop it on the canvas: the package is a verified community node, nothing to install. On self-hosted n8n, add n8n-nodes-nilyo from Settings then Community nodes. Create a personal token in Nilyo under Agent access and store it in a credential named Nilyo API.
Resolve the calendar, then list the window
List Calendars returns the exact ids; List Events takes one, plus the window you care about. Never pass a display name: the ids are what the provider indexes on, and a renamed calendar keeps its id while a label changes under you. The reminder template in the Nilyo library follows exactly that order.
Pair it with a provider that writes
The useful pattern is calendar in, message out: list the events due in the next window, extract the guests, then send on WhatsApp with email as the fallback. The calendar is the read side and another provider is the write side, which is also why the calendar node being read-only rarely blocks a workflow.
Or attach it to an AI Agent
The node can be attached to an n8n AI Agent as a tool, so the agent picks the operation and the arguments itself — useful when the workflow is a question in natural language rather than a fixed sequence. The tool variant of the node type is required for that; the plain type imports but silently drops the connection.
“Every morning, list tomorrow’s meetings and send me the guests.”
“Two hours before an event, remind each attendee on WhatsApp.”
Common questions
Can the n8n node create a calendar event?
Not today. The calendar resource exposes List Calendars and List Events. Creating, moving, cancelling or answering an event is available through the MCP server from a chat client, Zapier or Make.
Which calendars work?
Google and Microsoft accounts connected in Nilyo. One credential in n8n reaches every connected account, selected per step by its account id.
Do I need to install anything on n8n Cloud?
No. Nilyo is a verified community node, so you add it from the canvas. Self-hosted instances install n8n-nodes-nilyo from Settings then Community nodes.
Can an AI Agent use it?
Yes, attached as a tool, provided the tool variant of the node type is used — with the plain type the editor imports the node and drops the agent connection silently.
How Calendar works with Nilyo
Connection. Included with a Google or Microsoft sign-in: one identity gives email and calendar and counts as one account.
What your agent can do. Calendars, events in a date range, creating, updating, cancelling and restoring events, RSVPs.
Pacing and safety. No local budget.
- Combine with LinkedIn and email for meeting briefs: attendees are matched to profiles and past conversations.
All Calendar guides
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.