Teamup Calendar
SchedulingConnect AI agents to Teamup, a shared group calendar for teams. Agents create, update, and delete events, search the schedule, and list sub-calendars so group calendars stay accurate without manual editing.
What This Integration Enables
Teamup does not belong to the same family as the rest of the scheduling catalog, and pretending otherwise leads people to the wrong tool. There are no customers here, no services, no slots, and no availability endpoint. Teamup is a shared group calendar, and the object it is built around is the sub-calendar: a lane on a single calendar representing a team, a vehicle, a room, a project, or a category, each with its own color and its own audience. That is why organizations reach for it. Everyone looks at one calendar, and everyone sees only the lanes that concern them. Get Sub-Calendars returns those lanes with their IDs and active status, and Get Calendar Configuration exposes the calendar timezone and the custom event field definitions, which is how a flow discovers what a given calendar actually tracks beyond a title and a time.
The event operations are shaped to match. Get Events returns a date range with recurring events expanded into individual instances, so a flow reasoning about next Tuesday gets next Tuesday rather than a recurrence rule to interpret. Search Events runs free text across title, notes, location, and who fields using Teamup's own query syntax, with field filters and boolean operators, which is a far better way to find one entry than paging a range. Create Event, Update Event, and Delete Event handle the writes, all three aware of recurrence. Two behaviors are worth reading carefully before you build: Update Event is a full write, and Delete Event returns an undo ID. Agents read, search, and create without supervision. Rewriting an entry that a team is already planning around goes to a person, which is the human-in-the-loop default FlowRunner builds around. Every operation is built and verified against the Teamup REST API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Turning a Request in Chat Into a Calendar Entry
A supervisor posts in Slack that Tuesday's van run needs to move to Wednesday morning. The agent runs Search Events with the vehicle name and the date range rather than asking anyone for an event ID, then Get Event on the match to load its full record, its recurrence rule, and its version string. It runs Get Events across Wednesday on the same sub-calendar to check what else that vehicle is committed to. Then it assembles the proposal, including whether the entry is part of a repeating series, and posts it back to the supervisor. What the agent has removed is not the decision. It is the fifteen minutes of scrolling that used to precede it.
A Weekly Picture the Team Reads Somewhere Else
Every Sunday evening the agent runs Get Sub-Calendars to pick up any lanes added during the week, then Get Events across the next seven days for each one. Recurring entries come back expanded, so the output is a real week rather than a set of rules. The agent writes it to Google Sheets with one tab per sub-calendar and posts the coverage summary to Microsoft Teams. Days where a lane has no entry at all are called out at the top as automation exceptions, because an empty lane is usually an oversight rather than a decision.
Bringing an External Roster Onto the Shared Calendar
A field team's assignments live in a workforce system that the rest of the business cannot see. Each morning the agent reads the day's assignments and runs Get Calendar Configuration to learn which custom fields this calendar defines. It then creates one entry per assignment with Create Event: the crew in the who field, the site in the location field, the work order number in a custom field, and the region's sub-calendar as the lane. Entries that already exist are found first with Search Events so the calendar does not fill with duplicates. Because Teamup exposes no webhooks, this runs on a schedule rather than on an event, which suits a roster that is settled once a day.
Human-in-Loop Highlight
Teamup inverts the usual risk order, and it catches people out. Delete Event returns an undo ID that can restore what was removed, so a deletion here is recoverable. Update Event is the one that is not. Teamup treats an update as a full write, which means start, end, and sub-calendar assignment must be resupplied on every call along with whatever changed. Anything the agent does not carry forward from Get Event is not preserved, it is overwritten: the notes body, the location, the who field, the custom field values a coordinator filled in last week. Recurrence Edit Mode widens the blast radius from there, deciding whether the write lands on one instance, on this and every future instance, or on the entire series stretching backward and forward. So the agent gates the update. It posts to the calendar owner: "Van 4 on Tuesday 07:00 is instance 6 of a weekly series and carries a work order number in a custom field. Moving it to Wednesday 09:00. Apply to this instance only, this and all future instances, or the whole series?" Reads, searches, new entries, and deletions with their undo IDs recorded all run on the agent's own judgment. Rewriting an entry a team has already planned around, at a scope the agent chose for itself, does not.
Agent Capabilities
8 actionsEvents
6- Get Events Returns calendar events within a date range, optionally restricted to selected sub-calendars, with recurring events expanded so every instance inside the range comes back individually. Dates default to today when omitted.
- Search Events Searches events by free text across title, notes, location, and who fields within an optional date range, with paging. The query supports Teamup's own syntax including field filters, quotes, and boolean operators.
- Get Event Fetches a single event by identifier with full details, including title, times, sub-calendar assignment, notes, and recurrence rule. Run it before any update so the write carries forward everything the entry already holds.
- Create Event Creates a new event on one or more sub-calendars from a start and end datetime. Supports all-day events, a notes body, location, the who field, and a recurrence rule in iCal RRULE format, and returns an undo ID with the created event.
- Update Event Updates an existing event. Teamup treats this as a full write, so start, end, and sub-calendar assignment must be supplied along with any changed fields. The version string from Get Event guards against concurrent edits, and Recurrence Edit Mode sets the scope.
- Delete Event Deletes an event by identifier and returns an undo ID that can restore it. Recurrence Edit Mode controls whether the removal covers only this instance, this and future instances, or the whole series.
Sub-Calendars
1- Get Sub-Calendars Returns the sub-calendars defined on the calendar, meaning the resources or categories, each with its ID, name, color, and active status. These IDs are required when creating, updating, or filtering events.
Calendar
1- Get Calendar Configuration Returns the calendar configuration, including its title, default timezone, sub-calendars, and custom event field definitions. The read that tells a flow what this particular calendar tracks before it starts building entries.
Frequently Asked Questions
What can FlowRunner do with Teamup Calendar?
FlowRunner agents can run Get Events, Search Events, and Get Event in Teamup Calendar, plus 5 more actions.
Does connecting Teamup Calendar to FlowRunner require OAuth?
No. Teamup Calendar connects to FlowRunner with an API key, no OAuth flow required.
Can Teamup Calendar trigger a FlowRunner workflow automatically?
Teamup Calendar doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Teamup Calendar
$100 in credits. No card required. Connect in minutes.