Extension Email Calendar Events

作者 caffeinelabs362f51ae96f0無授權條款2 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Support for organising events/meetings and sending invitations by email.

僅含說明CommunicationProductivity & Workflow
AI 產生的概覽

為 Caffeine AI 應用程式加入 Motoko 行事曆事件增刪改查與電子郵件 iCalendar 邀請功能。

功能
此技能說明一個預製 Motoko 模組，用於建立、更新、取消、刪除、取得與列出行事曆事件，並以電子郵件寄送 iCalendar 邀請給參與者。它會為每位參與者建立 iCalendar 附件，並透過郵件閘道或傳輸容器寄送。內容也涵蓋主辦人模型、更新與取消的序號處理，以及從舊版本移轉的步驟。
適用情境
適用於建置需要安排會議或活動並以電子郵件寄送行事曆邀請的 Caffeine AI 後端。適合需要事件增刪改查加上邀請寄送的應用程式，包括讓參與者行事曆移除事件的取消操作。
執行需求
需要 Motoko 工具鏈以及 mops 套件 caffeineai-email-calendar-events、caffeineai-email 和 caffeineai-authorization，並需要 Caffeine AI plus 或 pro 訂閱。寄送郵件在啟用時使用郵件閘道及 INTEGRATIONS_GATEWAY_URL 和 INTEGRATIONS_GATEWAY_API_KEY，否則使用傳輸容器。不附帶指令碼，僅為說明與模組參考。

Email — Calendar Events

Calendar events email extension for Caffeine AI.

Overview

This skill adds support for organising events/meetings and sending iCalendar invitations by email. It provides CRUD operations for calendar events and email-based invitation delivery.

Backend

This component is for organising events/meetings and sending invitations by email

  • Internally it builds and attaches an iCalendar file to each attendees's email
  • This component does not yet support receiving RSVPs from attendees

To add/update/cancel/delete/get/list calendar events

  • Use the prefabricated module mo:caffeineai-email-calendar-events/calendarEvents.mo which cannot be modified.
mo:caffeineai-email-calendar-events/calendarEvents.mo
module {  public type CalendarEvent = {    uid : Text;    sequence : Nat32;    method : CalendarEventMethod;    summary : Text;    description : Text;    location : Text;    startTime : Nat64;    endTime : Nat64;    organizer : Organizer;    attendees : [Attendee];  };
  public type CalendarEventMethod = {    #request;    #publish;    #cancel;  };
  // The organizer is the sender: the invitation comes from  // `<fromUsername>@<app domain>` and that mailbox, under this display name,  // is the ICS ORGANIZER and the first guest. Only attendees carry addresses.  public type Organizer = {    name : ?Text;  };
  public type Mailbox = {    email : Text;    name : ?Text;  };
  public type Attendee = {    who : Mailbox;    role : CalendarEventRole;  };
  public type CalendarEventRole = {    #chair;    #required;    #optional;    #notParticipating;  };
  public type State = {    var events : List.List<CalendarEvent>;    var uidMap : Map.Map<Text, Nat>;  };
  public func add(    self : State,    uid : Text,    summary : Text,    description : Text,    location : Text,    startTime : Nat64,    endTime : Nat64,    organizer : Organizer,    attendees : [Attendee]  ) : ?CalendarEvent;
  // update, addAttendees, removeAttendees and cancel store the change with  // the next sequence number and return the stored record. Send that record:  // calendars apply an update or a cancellation only when its sequence is  // higher than the one they hold.  public func update(    self : State,    uid : Text,    summary : ?Text,    description : ?Text,    location : ?Text,    startTime : ?Nat64,    endTime : ?Nat64,    organizer : ?Organizer,    attendees : ?[Attendee]  ) : ?CalendarEvent;
  public func addAttendees(    self : State,    uid : Text,    attendees : [Attendee]  ) : ?CalendarEvent;
  public func removeAttendees(    self : State,    uid : Text,    attendees : [Text]  ) : ?CalendarEvent;
  public func cancel(self : State, uid : Text) : ?CalendarEvent;
  public func delete(self : State, uid : Text);
  public func get(self : State, uid : Text) : ?CalendarEvent;
  // Iterate over all calendar events older to newer  public func iter(self : State) : Iter.Iter<CalendarEvent>;
  // Iterate over all calendar events newer to older  public func reverse(self : State) : Iter.Iter<CalendarEvent>;
  // One invitation copy per attendee from `<fromUsername>@<app domain>`, the  // organizer's mailbox, through the mail gateway or the transport canister.  public func sendCalendarEvent(fromUsername : Text, event : CalendarEvent) : async { #ok; #err : Text };}

For sending calendar event invitations to attendees by email

  • Use the sendCalendarEvent function of the same module. It sends one copy per attendee through the mail gateway when the canister has the gateway key (INTEGRATIONS_GATEWAY_URL / INTEGRATIONS_GATEWAY_API_KEY, injected by the platform where the gateway is enabled) and through the transport canister otherwise; the app code is the same either way. caffeineai-email is a dependency of this package, and the app does not call it for calendar mail.
  • fromUsername is the local part of the sender only, such as events or no-reply. The invitation comes from <fromUsername>@<app domain>, and the app domain is the project's own, resolved by the mail gateway. Never pass a full address and never read or guess the domain in the app.
  • The organizer is that same mailbox. CalendarEvent.organizer carries only a display name, { name = ?"Community Team" }, shown as the ICS ORGANIZER and the first guest, so calendars see the invitation arrive from its organizer. Attendees are the only mailboxes with addresses; the organizer receives a copy only when also listed as an attendee. Do not model the organizer as a user with an email address.
  • It returns #ok once the invitation was accepted for every attendee, otherwise #err(error) with the error text.

Example usage for an app which can add/update/cancel/delete/get/list calendar events and send invitations to them by email

motoko
import Runtime "mo:core/Runtime";import Principal "mo:core/Principal";import Map "mo:core/Map";import Random "mo:core/Random";import Set "mo:core/Set";import Iter "mo:core/Iter";import Option "mo:core/Option";import Text "mo:core/Text";import AccessControl "mo:caffeineai-authorization/access-control";import MixinAuthorization "mo:caffeineai-authorization/MixinAuthorization";import CalendarEvents "mo:caffeineai-email-calendar-events/calendarEvents";import Uuid "mo:caffeineai-email-calendar-events/uuid";
actor {  public type UserProfile = {    name : Text;    email : Text;  };
  // Include authorization component  let accessControlState : AccessControl.AccessControlState;  include MixinAuthorization(accessControlState, null);
  // Store a map of caller principal to UserProfile  var userProfiles : Map.Map<Principal, UserProfile>;
  // Store a set of emails for uniqueness check  var emails : Set.Set<Text>;
  // Store the calendar events  let calendarEvents : CalendarEvents.State;
  public shared ({ caller }) func registerUser(name : Text, email : Text) : async () {    // Check if the user already exists    if (userProfiles.containsKey(caller)) {      Runtime.trap("User already registered");    };
    // Check if the email is already used    if (emails.contains(email)) {      Runtime.trap("Email already taken");    };
    // Add a user record    userProfiles.add(      caller,      {        name;        email;      }    );    emails.add(email);  };
  public shared ({ caller }) func addCalendarEvent(summary : Text, description : Text, location : Text, startTimeMs : Nat64, endTimeMs : Nat64) : async () {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can add calendar events");    };
    let organiser = userProfiles.get(caller)      ?? Runtime.trap("Admin profile not found");
    let seed = await Random.blob();    let uid = Uuid.generateV4(seed);
    if (      calendarEvents.add(        uid,        summary,        description,        location,        startTimeMs,        endTimeMs,        { name = ?organiser.name },        userProfiles.values().map(          func({ name; email }) {            {              who = { name = ?name; email };              role = #required;            };          }        ).toArray()      ).isNull()    ) {      Runtime.trap("Failed to add calendar event");    };  };
  public shared ({ caller }) func updateEventDetails(uid : Text, summary : ?Text, description : ?Text, location : ?Text, startTimeMs : ?Nat64, endTimeMs : ?Nat64) : async () {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can update calendar events");    };
    if (      calendarEvents.update(        uid,        summary,        description,        location,        startTimeMs,        endTimeMs,        null,        null      ).isNull()    ) {      Runtime.trap("Failed to update calendar event");    };  };
  public shared ({ caller }) func addEventAttendees(uid : Text, attendees : [CalendarEvents.Attendee]) : async () {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can add calendar event attendees");    };
    if (calendarEvents.addAttendees(uid, attendees).isNull()) {      Runtime.trap("Failed to add attendees to calendar event");    };  };
  public shared ({ caller }) func removeEventAttendees(uid : Text, attendees : [Text]) : async () {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can remove calendar event attendees");    };
    if (calendarEvents.removeAttendees(uid, attendees).isNull()) {      Runtime.trap("Failed to remove attendees from calendar event");    };  };
  public shared ({ caller }) func cancelEvent(uid : Text) : async () {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can cancel calendar events");    };
    // The returned record carries method #cancel and the bumped sequence,    // which is what tells the attendees' calendars to drop the event.    let cancelled = calendarEvents.cancel(uid)      ?? Runtime.trap("Failed to cancel calendar event");
    switch (await CalendarEvents.sendCalendarEvent("events", cancelled)) {      case (#ok) {};      case (#err(error)) {        Runtime.trap("Failed to send the cancellation: " # error);      };    };  };
  public shared ({ caller }) func listEvents() : async [CalendarEvents.CalendarEvent] {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can list calendar events");    };
    calendarEvents.iter().toArray();  };
  public shared ({ caller }) func deleteEvent(uid : Text) : async () {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can delete calendar events");    };
    calendarEvents.delete(uid);  };
  public shared ({ caller }) func sendEventInvitation(uid : Text) : async () {    if (not (AccessControl.hasPermission(accessControlState, caller, #admin))) {      Runtime.trap("Unauthorized: Only admins can send calendar event invitations");    };
    let event = calendarEvents.get(uid)      ?? Runtime.trap("Calendar event not found");
    ignore await CalendarEvents.sendCalendarEvent(      "events",      event    );  };};

The migration chain head:

motoko
import Map "mo:core/Map";import Set "mo:core/Set";import AccessControl "mo:caffeineai-authorization/access-control";import CalendarEvents "mo:caffeineai-email-calendar-events/calendarEvents";
module {  type UserProfile = {    name : Text;    email : Text;  };
  type NewActor = {    accessControlState : AccessControl.AccessControlState;    var userProfiles : Map.Map<Principal, UserProfile>;    var emails : Set.Set<Text>;    calendarEvents : CalendarEvents.State;  };
  public func migration(_old : {}) : NewActor {    {      accessControlState = AccessControl.initState();      var userProfiles = Map.empty<Principal, UserProfile>();      var emails = Set.empty<Text>();      calendarEvents = CalendarEvents.new();    };  };};

Upgrading from the previous version

An app built with caffeineai-email-calendar-events 0.2.x re-pins with mops add [email protected] and mops add [email protected]. CalendarEvent.organizer is now an Organizer ({ name : ?Text }) instead of a Mailbox: the organizer address is the sender's, <fromUsername>@<app domain>, built by the mail gateway, so the app no longer supplies one. add and update take the new type, and an app that stored events adds a migration step that maps each stored organizer to { name = old.organizer.name }.

An app built with caffeineai-email-calendar-events 0.1.x re-pins with mops add [email protected] and mops add [email protected]. sendCalendarEvent keeps its signature but moves from EmailClient to this module (CalendarEvents.sendCalendarEvent), and the event types (CalendarEvent, Attendee, Mailbox, CalendarEventMethod, CalendarEventRole) are this module's; an app that imported them from EmailClient switches the import and drops EmailClient when nothing else uses it. Invitations are now composed and sent by the mail gateway. update, addAttendees, removeAttendees and cancel now return the stored record (with the bumped sequence) instead of the previous one, so an app that sends the returned record after a change sends the right sequence.

來源與署名

來源：caffeinelabs/skills位於skills/extension-email-calendar-events提交362f51a

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 caffeinelabs/skills 的技能

Writing Motoko

caffeinelabs

撰寫 Internet Computer 上 Motoko 後端程式的參考與架構指南，含 mops 工具鏈說明。

Software Development2今天更新

Migrating Motoko Actors

caffeinelabs

指導使用 mops 管理的遷移鏈進行 Motoko actor 遷移，以處理狀態與結構變更。

Software Development2今天更新

Troubleshooting Motoko Migrations

caffeinelabs

用於排查 Motoko 遷移鏈故障的參考，涵蓋相容性錯誤、凍結檔案與已轉換專案。

Software Development2今天更新

Extension Querying Oql

caffeinelabs

透過 icp CLI 查詢暴露 OQL 的 canister 的參考：讀取 schema、建立 JSON 查詢、解析 Candid 結果列。

Data & Analytics2今天更新

Extension Qr Code

caffeinelabs

透過預製 React hook 為 Caffeine AI 應用程式加入以相機為基礎的 QR Code 掃描功能。

Software Development2今天更新

Extension Object Storage

caffeinelabs

為 Caffeine AI Motoko 容器加入鏈下檔案與物件儲存，並在鏈上保留參照。

Software Development2今天更新

更多Communication技能

Internal Comms

anthropics

精選

依公司慣用格式撰寫內部溝通文件，例如 3P 更新、公司電子報、FAQ、狀態報告與事故報告。

Communication180K3 天前更新

Receiving Code Review

obra

指導代理接收程式碼審查意見：核實建議、釐清不明項目、以技術理由反駁，並逐項實作修正。

Communication296K今天更新

Social Publisher

affaan-m

透過 SocialClaw 工作區 API 在 13 個平台上排程與發佈社群媒體貼文。

Communication275K3 天前更新

Email Ops

affaan-m

以證據為基礎的信箱分流、草擬、寄送驗證與已寄郵件後續追蹤流程。

Communication275K3 天前更新

Customer Billing Ops

affaan-m

引導營運人員處理客戶帳務情境，例如重複訂閱、退款、流失排查與帳務入口恢復。

Communication275K3 天前更新

Plan Canvas

affaan-m

在本地瀏覽器畫布中開啟計畫或 HTML 產物，供人工標註、聊天並給出核准或要求修改的結論。

Communication275K3 天前更新