nextcloud / nextcloud/calendar

How to fetch shared calendar properties (creator, created time, last modified by, last modified time) via HTTP Request

Open
#7,681 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature: caldav
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce

Hi everyone,
I'm trying to retrieve shared calendar events using an HTTP Request node in N8N.
I need to get the following metadata for each event:
Creator (who created the event)
Created time
Last modified by
Last modified time
I know I can use REPORT request with a prop like:
<D:prop>
<D:getetag/>
<C:calendar-data/>
</D:prop>
But I couldn’t find any documentation on whether there are specific properties (like <C:created-by/>, <C:last-modified-by/>, etc.) that expose the creator or last modifier of a calendar event.
Does anyone know:
Are there any standard or extended WebDAV/CalDAV properties that return creator and last modified by info?
If so, what are the exact XML prop names I should use in the request body?
Is this dependent on the calendar server (e.g., Nextcloud, Google, Exchange)?
Any examples or working XML snippets would be super helpful.
Thanks in advance!

Expected behavior

How to fetch shared calendar properties (creator, created time, last modified by, last modified time) via HTTP Request

Actual behavior

How to fetch shared calendar properties (creator, created time, last modified by, last modified time) via HTTP Request

Calendar app version

No response

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

None

Database engine version

None

PHP engine version

None

Nextcloud version

No response

Updated from an older installed version or fresh install

None

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No project files or tests are identified; start by reviewing the linked Nextcloud Help discussion and the reported HTTP Request/CalDAV property requirements. Done would mean documenting whether creator, creation time, last modifier, and modification time are available, including exact XML property names and any server-specific limitations.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.