.ics feeds
Paste any calendar's .ics address so its busy time blocks your booking slots and its meetings reach Venom People: where to find the address in Google, Outlook, iCloud and TripIt, how fresh the data is, and how the address is kept.
Any calendar that can publish an .ics (iCal) address can block your slots: a partner's shared calendar, a TripIt trip list, a school calendar, an Outlook "publish" link or an iCloud public calendar. You paste the address once. Venom fetches the feed, reads every event in it (recurring events, exceptions, time zones and all-day events included) and treats the busy time like that of any other connected calendar.
Finding the address
Copy the address that ends in .ics, or starts with webcal://. Venom reads webcal:// as https://.
| Calendar | Where the address is |
|---|---|
| Google Calendar | On the web: Settings, then under "Settings for my calendars" pick the calendar, then "Integrate calendar". Copy Secret address in iCal format. Use the public address only if the calendar is public. |
| Outlook.com and Microsoft 365 | On the web: Settings, Calendar, Shared calendars, "Publish a calendar". Pick the calendar and how much to show ("Can view when I'm busy" is enough), select Publish, then copy the ICS link. |
| iCloud | On a Mac in Calendar, or on iCloud.com: share the calendar and tick Public Calendar, then copy the link. On an iPhone: Calendars, the (i) next to the calendar, Public Calendar, Share Link. |
| TripIt | Settings, then Calendar Feed. Turn the feed on and copy the subscription address. |
A secret address works without signing in, which is why Venom treats it as a password (below). If Google or Outlook says the address was reset, paste the new one with Change address.
Adding, changing and removing a feed
When you add a feed, Venom fetches it and reads it before saving anything. An address that is not a calendar (a sign-in
page, a 404, a file cut off mid-download) is refused with the reason, and nothing is stored. The feed becomes one
connected account with one calendar, named after the feed's own name (X-WR-CALNAME) unless you give it a label, and
read in the feed's own time zone (X-WR-TIMEZONE) when it names one.
Changing a feed's address fetches the new one first; if it can't be read, the old address stays. Removing a feed drops its busy time at once.
What is busy
- Each event's time from its start to its end. An event with a start time but no end takes no time and is not busy; an all-day event with no end lasts one day.
- Recurring events are expanded inside the time Venom keeps (a day ago to a year ahead) on the event's own clock, so a 09:00 meeting stays at 09:00 through a daylight saving change. Skipped dates, moved or cancelled instances, and "this and following" changes are followed.
- Free, transparent and cancelled events are not busy. Outlook's "Free" is free and its "Tentative" is tentative.
- Tentative events count as busy unless you turn that off for the calendar. All-day events do not count unless you turn that on: most all-day events are reminders, but a trip feed's are not, so turn it on for TripIt.
- A feed that publishes only free/busy periods (
VFREEBUSY) works too. - Times in Windows zone names ("Pacific Standard Time"), as Outlook writes them, are mapped to real time zones with the Unicode CLDR table, which is part of Venom and never downloaded. Times with no zone are read in the feed's zone, or in yours when the feed names none.
Event titles are kept only for your own week view. They never reach a booking page or an invitee.
Meetings in People
The same read also gives Venom People your meetings for the next seven days (Meetings in People):
each event's ATTENDEE and ORGANIZER addresses are matched to your people, and its LOCATION is kept as the place.
An hour after a meeting ends it is logged on the people matched in it, "via" the feed's label. An attendee who matches
nobody is only a count until the meeting has ended; then they wait in your own People review list (email and CN)
until you decide. Rooms and resources are skipped, and an event you declined is left out. Import past meetings in
People settings reads the feed once more and takes whatever past events it holds, back 24 months. At most 200 attendees
are read per event. A feed that publishes only free/busy periods has no attendees, and an event with none is matched by
its title. No extra request is made: when a feed keeps answering "not modified", Venom reads it in full once every 12
hours so new meetings still reach People.
How fresh it is, and why
| When | What happens |
|---|---|
| Every 10 minutes | Venom asks each feed whether it changed. The time varies by up to 25% either way so feeds aren't all asked at once. A feed that sets REFRESH-INTERVAL or X-PUBLISHED-TTL is asked that often, but never more than once every 5 minutes. |
| A booking page opens | Your feeds are fetched again, at most once every 2 minutes each. |
| Before a booking is confirmed | The same, so the last check is made against current data. |
Venom sends the feed's ETag and Last-Modified back with each request. A feed that hasn't changed answers "not
modified" and costs nothing more; one that sends the same file again is not read again. Every 12 hours the request goes
without them, so the feed is read again for People (above).
A feed can't be fresher than its publisher. Google, Outlook and iCloud regenerate a published file on their own schedule, sometimes many minutes after you edit an event. Connected Google accounts, which Venom reads directly, are quicker.
When a feed fails (the address stops working, the server is down, the file is malformed), the account shows error with the reason in words and Venom keeps the last busy time it read, because showing you busy is safer than showing you free. It tries again every 30 minutes and clears the error once the feed reads.
Limits
| Limit | Value |
|---|---|
| Feed size | 10 MB |
| Busy blocks in the time kept | 50,000 |
| Time to read one feed | 2 seconds of CPU |
| Fetch | 10 seconds, at most 3 redirects |
| Feeds per person | 50 |
Past a limit the feed is not used and shows the reason, for example "The feed has more than 50,000 events in the time read". A holiday calendar for every country is the usual cause; subscribe to the one you need.
How the address is kept
A feed address is a secret link: anyone who has it can read the calendar. Venom stores it sealed in your organisation's
vault (AES-256-GCM under a key for your organisation, bound to the feed's account) and never shows it again, not in the
app, the API, an MCP tool or a log. Feeds therefore need a vault key on the cloud (VENOM_VAULT_KEYS); without one,
adding a feed says so.
On the hosted cloud Venom only fetches public https addresses: every address, and every redirect, is checked so that
a feed can't point the cloud at a private network or a metadata service. Self-hosted for development
(make cloud-dev), a feed on localhost works. Nothing contacts a feed until you add it.
For builders and agents
The console calls these routes with your session:
| Route | What |
|---|---|
POST /api/workspace/calendar/ics |
{ "url": "webcal://…", "label": "TripIt" }. 201 with the account, its calendar and busy_blocks; 422 feed_invalid with the reason when the feed can't be read |
PATCH /api/workspace/calendar/ics/{id} |
{ "label": "…" } and/or { "url": "…" } |
DELETE /api/workspace/calendar/ics/{id} |
204 |
Agents use the calendar MCP at /workspace/mcp/calendar (claude mcp add --transport http venom-calendar https://<cloud>/workspace/mcp/calendar) with a member's credential: calendar_feed_list, calendar_feed_add,
calendar_feed_update and calendar_feed_remove. Reading needs calendar:read, changes need calendar:write. A team
key is refused, because calendars are personal.