nextcloud / nextcloud/forms

Integrate Nextcloud Forms submissions with shared Calendar events

Open
#2,971 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement integration
Dominant language
JavaScript
Stars
382
Forks
127
Avg merge
19h 31m
Merged PRs (30d)
75

Description

Hi team,

I’d like to request (or explore) a feature that allows Nextcloud(v30) Forms to automatically create or update Calendar events based on submitted form data.

Use Case

Our team frequently travels internationally, and we currently maintain a shared Nextcloud Calendar(v6) so everyone can see who is traveling to which country on which dates.
However, filling in travel information directly in the Calendar is less convenient than using Forms(v5), which offer structured fields, easier input, and better export/analysis options.

The idea is:

A shared Form (e.g., “Business Trip Record”) includes fields like:

Employee Name

Destination Country

Start Date

End Date

Notes or Purpose

When a team member submits or updates a form entry, the data should automatically create or update an event in a shared Calendar (e.g., “Team Travel Calendar”).

This would allow everyone to still use their preferred calendar clients (like Outlook) to view team availability while keeping structured data in Forms for analytics.

Benefits

Centralized data collection via Forms

Automatic synchronization with shared Calendar

Improved data consistency, exportability, and team visibility

Possible Implementations

Direct integration between Forms and Calendar (ideal)

A workflow bridge (maybe via Flow or an app hook) that triggers when a form is submitted

Webhook or API support for creating/updating calendar events based on form responses

Question

Has anyone implemented something like this, or is there any plan to make Forms interact with Calendar or Flow in this way?

Thank you for considering this — I believe it would be a very useful enhancement for teams managing travel or scheduling tasks.

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

Start by reviewing how Forms submissions and updates are handled, then investigate the app-hook, webhook, API, and Flow integration points named in the issue. Define how submitted fields map to shared Calendar event creation and updates, including edits, before determining the implementation scope; done means a decided integration approach or working synchronization.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.