What is the primary function of the I Cal node in n8n workflows?
The I Cal node allows you to read, parse, and process calendar data, typically in the iCalendar format. It is essential for building workflow Integrations that rely on scheduling or event management.
How can the I Cal node be used as a trigger for a workflow?
While the I Cal node itself usually processes existing calendar data, it can be combined with a poll trigger or a time-based trigger node to check for newly added or updated events, effectively acting as a data source for subsequent actions.
What kind of calendar data does the I Cal node handle?
This node is designed to handle standard iCalendar data (often found in files with .ics extension). It parses calendar components like VEVENTS, VTODOs, and VJOURNALS, structuring them for use in the workflow.
Can the I Cal node integrate with external calendar services?
The I Cal node processes the data format. For direct Integrations with services like Google Calendar or Outlook, you would typically use the dedicated service node to retrieve the raw iCalendar data, which the I Cal node can then process.
Is the I Cal component intended for use only as a starting node or can it be placed mid-workflow?
The I Cal node is highly effective mid-workflow. It is often placed after a trigger or a data retrieval node (like an HTTP node) to parse iCalendar files downloaded from a web source before passing the structured data to other workflow nodes.