ics-to-org
Sync iCalendar events to org-mode files while preserving your notes.
What's New in v1.0.0
This is a major rewrite with significantly improved reliability and simplicity:
- ✅ No more Node.js dependency - Pure Python implementation using the
icalendarlibrary - ✅ Cleaner org format - ICS descriptions stored in
:DESCRIPTION:property, user notes go directly in the event body - ✅ Bulletproof merge logic - Calendar data always updates, user notes always preserved
- ✅ Better timezone handling - Proper handling of UTC and all-day events
- ✅ Comprehensive tests - Real .ics files and .org examples with full integration testing
Installation
Simple single-step installation:
pip install ics-to-org
Or with uv:
uv tool add ics-to-org
Usage
After installation, you can run the tool:
ics-sync --ics-url "https://outlook.office365.com/..." \
--org-file "meetings.org" \
--days-forward 30 \
--days-backward 7
Or run it directly with uvx (no installation needed):
uvx --from ics-to-org ics-sync --ics-url "https://calendar.google.com/calendar/ical/..." \
--org-file "calendar.org"
Command-line options:
| Option | Description | Default |
|---|---|---|
| –ics-url | URL of the iCalendar feed (required) | - |
| –org-file | Path to the org file to update (required) | - |
| –days-forward | Number of days forward to fetch | 30 |
| –days-backward | Number of days backward to fetch | 7 |
| –debug | Enable debug logging | false |
How It Works
The sync process:
- Fetches your calendar from the ICS URL
- Parses your existing org file to extract user notes
- Merges calendar updates with your preserved notes:
- Calendar data (title, time, location, description) always gets updated
- Your personal notes are always preserved
- Removed events are marked as
CANCELLED:but kept with your notes - New events are added cleanly
- Writes the updated org file with events sorted by date
Org File Format
Events are stored in a clean, standard org format:
* Team Meeting
:PROPERTIES:
:UID: meeting123@company.com
:LOCATION: Conference Room A
:DESCRIPTION: Weekly team sync and project updates
:STATUS: CONFIRMED
:CATEGORIES: Work
:END:
<2025-01-15 Wed 14:00-15:00>
My personal notes for the meeting:
- Remember to bring the quarterly report
- Ask about the new project timeline
- Discuss vacation schedule
Action items:
- [ ] Finish the client proposal
- [X] Review the budget numbers
Key features of the format:
:DESCRIPTION:contains the calendar description (read-only):UID:provides the unique identifier for syncing- Event body contains your personal notes in any format (markdown, org-mode, plain text)
- All-day events show as
<2025-01-20 Mon> - Timed events show as
<2025-01-15 Wed 14:00-15:00>
Examples
Basic sync with default settings
ics-sync --ics-url "https://calendar.google.com/calendar/ical/..." \
--org-file "calendar.org"
Longer time range with debug output
ics-sync --ics-url "https://outlook.office365.com/owa/calendar/..." \
--org-file "work-calendar.org" \
--days-forward 60 \
--days-backward 14 \
--debug
Using with uvx (no installation required)
# Run directly from PyPI without installing
uvx --from ics-to-org ics-sync --ics-url "https://example.com/calendar.ics" \
--org-file "my-calendar.org" \
--days-forward 60 \
--debug
Using with uv run (in a project)
uv run ics-sync --ics-url "https://example.com/calendar.ics" \
--org-file "my-calendar.org"
Using with local .ics files
If you can't access the calendar URL directly (common with Outlook), download the .ics file and use it locally:
# Using a local file path
ics-sync --ics-url "/path/to/downloaded/calendar.ics" \
--org-file "calendar.org"
# Or with file:// URL
ics-sync --ics-url "file:///path/to/calendar.ics" \
--org-file "calendar.org"
Troubleshooting
Outlook/Office365 Calendar Issues
If you're having trouble accessing your Outlook calendar:
- Download the .ics file manually: Go to Outlook Web → Calendar → Share → Publish Calendar → Copy the ICS URL → Download it with your browser
- Use the downloaded file:
ics-sync --ics-url "/path/to/calendar.ics" --org-file "events.org" - Check calendar permissions: Make sure your calendar is set to "Public" with "Can view all details" in Outlook settings
- Try the debug flag: Run with
--debugto see detailed error messages
Common Error Messages
- *"Received HTML response instead of ICS data"*: The calendar URL requires authentication or is private
- *"Authentication required"*: Calendar is not publicly accessible
- *"Object moved to here"*: Calendar URL has redirects/authentication issues
For these issues, downloading the .ics file manually is the most reliable solution.
Testing
The project includes comprehensive tests with realistic examples:
pytest tests/ -v
Test coverage includes:
- ✅ Unit tests for all core functions
- ✅ Integration tests with real .ics files and .org files
- ✅ Edge cases like timezone handling, malformed events, empty calendars
- ✅ User note preservation across various markdown and org-mode formats
- ✅ Complete workflows from ICS fetch through merge to org file output
Migration from v0.x
If you're upgrading from the old version:
- Remove the icsorg dependency:
npm uninstall -g icsorg - Update your scripts: Remove
--authorand--emailparameters (no longer needed) - Review your org files: The new format stores descriptions in properties instead of agenda blocks
The new format is cleaner and more reliable, but you may want to manually clean up old agenda blocks if desired.
Development
# Clone the repository
git clone https://github.com/andyreagan/ics-to-org
cd ics-to-org
# Install with uv (recommended)
uv sync
# Run tests
uv run pytest
# Build package
uv build
Contributing
Contributions are welcome! Please:
- Add tests for any new functionality
- Ensure all tests pass:
uv run pytest - Follow the existing code style
- Update documentation as needed
License
MIT License. See LICENSE file for details.
Metadata
Release files for ics-to-org 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ics_to_org-1.0.6.tar.gz | 19.5 kB | With provenance | Details for ics_to_org-1.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ics_to_org-1.0.6-py3-none-any.whl | Python 3 | none | any | Details for ics_to_org-1.0.6-py3-none-any.whl |
Total release size: 31.3 kB
Release files / ics_to_org-1.0.6.tar.gz
| Download URL | ics_to_org-1.0.6.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96995be23784006dedca0fc320a23e6c11456f09a023d8f8dcde41380ce18486
|
|
BLAKE2b-256 checksum How to use checksums |
416eb9280851fc2fc7387d9befd997fe72733def9cbc31178432118dbe0ee130
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2026.
Transparency logRelease files / ics_to_org-1.0.6-py3-none-any.whl
| Download URL | ics_to_org-1.0.6-py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51264305072babb15aafd10a8620c678deb2d24b95e98d48c73a539c4421ba14
|
|
BLAKE2b-256 checksum How to use checksums |
b0edfa2b80e3cd413bd71bf024374d6719cf6b7a59a161a17a9718b24e35b3dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2026.
Transparency logSecurity for ics-to-org 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ics_to_org-1.0.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.