Platforms / choose the right integration surface
Bring calendar capabilities into the application you already own. Use the released Salesforce distribution, embed the UI in a web app, or call the engine without a browser.
Ready distribution
Released unlocked package, LWC, Apex over standard Event records, and an installation and permissions guide.
Developer building blocks
Core and Interface packages plus example projects. Other platform starters are not equivalent packaged integrations.
One library / different host boundaries
Fetch and authorize events using your platform’s identity and data layer.
Map IDs, dates, fields, and mutation callbacks. Persist changes deliberately.
Use Core for reusable event, recurrence, query, and conflict logic.
Render the calendar component or expose headless operations to application code.
Host compatibility requires host-specific validation. No library replaces your platform’s identity, permissions, content-security policy, or deployment checks.
Developer examples
These repository examples show integration patterns. They are intentionally minimal starters, not supported products or a claim of verified production compatibility in your account.
A vanilla Vite example for embedding the Web Component in your application. Start with local events, then connect your authorized data layer.
Verify record mapping, event callbacks, persistence, and keyboard interaction in your app.
An example using Core for recurrence expansion, conflict detection, and ICS export in an edge handler.
Review the handler, runtime limits, request authorization, and workload size before deployment.
A packaged calendar interface for an extension popup, with vendored assets and an example manifest.
Review requested extension permissions and validate the manifest and content-security policy.
A calendar web-part starting point for Microsoft 365 pages and Teams tabs. Adapt its data and deployment model to your tenant.
Validate the SPFx toolchain, tenant deployment, identity, and data permissions.
A widget example over ServiceNow table data. Your instance determines records, access rules, and supported portal behavior.
Review ACLs, table queries, field mappings, and the target instance’s widget policies.
A sprint-calendar example presented through Forge Custom UI. Use it as an implementation reference for your own application.
Verify scopes, host integration, static assets, and deployment against current Forge requirements.
The mapping is yours
Transform authorized source records into calendar events. A snapshot updates the view; it is not a request to write those records back to the source system.
Read integration documentation// Illustrative mapping: adapt these fields to your schema.
const events = authorizedRecords.map(record => ({
id: String(record.id),
title: record.subject,
start: record.startsAt,
end: record.endsAt,
}));
calendar.setEvents(events);
// Separately authorize and persist user changes.
// Use your platform's own API and access controls.Interoperability, precisely
Core supports file import and export. An ICS file is not a connected Apple, Google, or Microsoft account. Live account synchronization is not shipped.
An agent can use the same headless engine through an application-owned adapter. Authorization, storage, and execution remain your application’s responsibility. The separate scoped-tool adapter is a private prototype, not a public hosted service.
Lightning Web Security is required for the third-party custom elements used by the Salesforce integration. Legacy Lightning Locker is not supported. Use the dedicated Salesforce guide for Apex permissions, package contents, and validation scope.
Try the behavior before the integration