FFlow
RUStart free

All nodes/Integrations/Calendar

Calendar Multiget

REPORT calendar-multiget for a list of hrefs.

Calendar Multiget▶
Calendar storeSuccess
Error

Type in the graph: calendar_multiget

Exec

An error branch can be enabled (expose_error_output) to handle failures on their own path.

Ports can be split into separate execution and data handles.

Try it

Minimal working workflow

Entry
Calendar Multiget▶
CalDAV Config
Exit▶
  • Execute
  • Data
  • Execute + Data
Press “Copy nodes”, open the editor and hit Ctrl+V on the canvas.

Pick your own connection or knowledge base first — the graph carries REPLACE_ME.

When to use it

Fetches several calendar objects in a single request. For one address Get Calendar Event is simpler; for a search by time use Calendar Query, which already returns parsed fields. Multiget earns its place when the list of addresses came from somewhere else — a variable, a database, a model — or when the found events need the full iCalendar that query results do not carry.

How it works

The node makes one request against one collection. Addresses are listed in “Event hrefs”, comma- or newline-separated; at most 50 per call, otherwise the node stops with a VALIDATION code before contacting the server. A blank “Calendar collection URL” means the connection’s default calendar.

The output carries items: each element has href, etag, ics and a parsed summary — or null when the server sent no body.

Common mistakes

  • The answer may be shorter than the list. An address that does not exist on the server simply does not come back, with no error raised. If that matters, compare the length of items against your own list.
  • The server decides the order. Assuming items[0] matches the first address in the field is unsafe — match on href.
  • The addresses must live in the named collection. One request goes to one collection; events from two calendars mean two nodes.
  • 50 is a hard ceiling. Split a longer list into chunks and walk them with For each.
  • A list where a string is expected. The field is a template that takes text: join an array from another node, {{ nodes.<id>.output.hrefs | join(",") }}, or the field ends up holding the array’s own printed form.

Inputs

PortWirePayloadNotes
Calendar storecalendar_storeDatadata—

required

Outputs

PortWirePayloadNotes
SuccessoutputExecute + Dataexecute_dataobject
Erroron_errorExecute + Dataexecute_data—

shown when expose_error_output = true

Configuration

FieldTypeDefaultDescription
CalDAV connectionconnection_idstring""

Saved workspace CalDAV connection, so a simple calendar graph does not need a separate CalDAV Config node. A node wired to the 'calendar_store' port wins over this field.

connection: caldavoverridden by port: calendar_store

Calendar collection URLcalendar_urlstring""

Collection URL to work with, e.g. https://cloud.example/remote.php/dav/calendars/user/personal/. Leave empty to use the default calendar URL of the connected CalDAV connection; discover URLs with the List Calendars node.

supports templates

Event hrefshrefsstring""

Hrefs to fetch, comma- or newline-separated, as returned by Calendar Query. At most 50 per call.

supports templates

Shared fields

Every node has these three — the platform adds them, not the node author.

  • expose_error_output — When enabled, show an execution output to connect nodes that run if this step fails.
  • split_ports_in — Show separate execution and data input handles instead of one combined port.
  • split_ports_out — Show separate execution and data output handles instead of one combined port.