ics-parser

n8n node to parse ICS calendar files and query events

Package Information

Released: 6 mo ago
Downloads: 9 weekly / 58 monthly
Latest Version: 3.1.1
Author: sebse

Documentation

n8n-nodes-ics-parser

version repo

n8n node to parse ICS calendar files and query events

This node integrates @sebse-tools/ics-parser into n8n workflows, enabling parsing and querying of iCalendar (.ics) data directly inside your automations.

Parameters

Parameter Type Description
Input Type Options Binary File or ICS String.
Input Data Field Name String Binary only. Name of the binary field on the input item containing the .ics file.
ICS String String String only. Raw ICS calendar content.
Start Date DateTime Start of the date range, inclusive.
End Date DateTime End of the date range, inclusive.

Output. One item per event occurrence found in the range.

Usage

Typical workflow: Fetch and Query

HTTP Request  →  ICS Parser
  1. HTTP Request node. GET your calendar URL, e.g. a CalDAV public share or a .ics file URL. Set Response Format to File to receive binary output, or Text to pass the raw string.

  2. ICS Parser.

  • Binary file input: set Input Type to Binary File and Input Data Field Name to data.
  • Text input: set Input Type to ICS String and map the response body to ICS String via an expression, e.g. {{ $json.body }}.
  • Set Start Date and End Date using expressions or fixed values, e.g. {{ $now }} and {{ $now.plus(7, 'days') }}.

Example. Weekly agenda digest

Schedule Trigger (every Monday)
  → HTTP Request (fetch calendar .ics)
  → ICS Parser
      Input Type:  Binary File, field "data"
      Start Date:  {{ $now.startOf('week') }}
      End Date:    {{ $now.endOf('week') }}
  → Send Email, Slack, etc.

Recent Changes

Version 3.1.0

  • c8401d3: make start and end dates optional

Version 3.0.2

  • 49c86bc: move n8n-workflow to optional peerDependencies

Version 3.0.1

  • a6e5800: move n8n-workflow to peerDependencies

Authors

  • sebse

License

This project is licensed under the AGPL-3.0-only License. See the LICENSE file for details.

Discussion