All nodes/Integrations/Calendar

CalDAV Config

Select a saved CalDAV connection for the workspace. Credentials are in the workspace settings.

Try it

When to use it

Reach for this node when one CalDAV connection serves several calendar nodes: the address is picked in a single place instead of being repeated on every node. A graph with one or two calendar nodes does not need it — each calendar node carries its own “CalDAV connection” field listing the same saved integrations.

Unlike Telegram Config, the Calendar store port is always visible on calendar nodes: there is no calendar to inherit from the run context, so the connection must be named explicitly — by a field or by a wire.

How it works

The node stores neither the server address nor the password. It references a CalDAV integration saved under “Settings → Integrations” and, at run time, hands the resolved connection over a data wire: base URL, username, discovery mode, calendar home and default calendar URLs, inbox and outbox URLs. The run log shows nothing but the connection name for this node — credentials reach neither the logs nor the event stream.

The node has no place of its own in the execution chain: it resolves lazily, when a calendar node asks for the connection.

Two things come from the connection that no node carries itself: the default calendar URL, used by every node whose “Calendar collection URL” is blank, and the outbox URL, without which Calendar Schedule cannot work.

Common mistakes

• The wire beats the field. With something wired into the Calendar store port, the “CalDAV connection” field on the node itself is ignored. If a node writes to the wrong calendar, check the incoming edge before the form.
• Neither wire nor field. Validation warns about this in the editor and blocks the run and the deploy: with no connection the node stops once the run reaches it.
• One calendar for everyone. Changing the default calendar URL on the integration changes the behaviour of every node whose collection field is blank, all at once.
• The kind is fixed. Only CalDAV connections are offered here; a WebDAV connection to the same server will not do, however similar the address looks.
• Check the connection in the settings. The “Check connection” button probes the saved integration and reports how many calendar collections it discovered. A failure there saves an hour of debugging the graph.

Inputs

—

Outputs

Configuration