Calendar consent
Make the calendar account, customer intent, and selected project explicit at the start of the connection journey.
Scheduling connection architecture
Carry scheduling intent from consent through reconciliation.
Connect calendar workflows to the product decisions that need them, with event state, policy boundaries, and recovery signals visible along the way.
Calendar & scheduling connection architecture
Set up Google Calendar with a clear product boundary.
Make account ownership, project context, health state, and recovery visible to the customer instead of burying the integration behind an opaque setup step.
Scheduling scope
Keep a calendar connection tied to the product workflow it serves rather than treating event data as a global workspace resource.
The product workflow
Google Calendar should be visible in the product, not hidden behind a connection status.
Explore the original Moira surfaces for the path from a customer-controlled connection to an observable workflow, with capability and recovery context alongside it.
1 of 3
Connection control plane
Give the customer a real surface for operating Google Calendar.
Moira keeps connected-account health, project-scoped credentials, delivery evidence, and a safe recovery route together in the customer console.
Explore the product
Use cases
Google Calendar product use cases
Use the provider as part of an ATS, CRM, or outreach workflow while retaining project and capability context at every step.
MMaya ChenConnection context updated
DDaan BakkerHealth state needs review
AAmara SinghProject event observed
ATS publisher
Keep Google Calendar connection context beside candidates, account health, and recruiter-owned recovery actions.
Explore use caseMMaya ChenConnection context updated
DDaan BakkerHealth state needs review
AAmara SinghProject event observed
CRM publisher
Put Google Calendar activity alongside the customer record so account teams can investigate the next safe action.
Explore use caseMMaya ChenConnection context updated
DDaan BakkerHealth state needs review
AAmara SinghProject event observed
Outreach publisher
Make Google Calendar a visible, policy-aware stage in a controlled multi-step outreach workflow.
Explore use caseDeveloper integration
Make the Google Calendar event contract explicit before it drives an action.
Associate each signal with a project, account, provider state, and recovery path. The result is an operable integration rather than a disconnected API response.
Read developer documentationconst event = await moira.events.verify({
projectId, provider: "google-calendar",
eventId: request.headers.get("x-moira-event-id"),
});
if (event.state === "attention_required") {
await queueRecoveryReview(event);
}Trust work in progress
Security and compliance status
These are current in-progress programs, not completed certifications, compliance guarantees, or a substitute for your own assessment.
Integration questions
Google Calendar integration FAQ
Answers describe product boundaries and operational recovery without making provider capability promises.
How does a Google Calendar connection begin?
A workspace member begins in the intended project context. Moira presents only the connection path and account state that the live provider registry and workspace policy permit.
Does this page guarantee a Google Calendar capability?
No. The page describes an integration architecture. Actual availability remains subject to configured provider paths, account state, entitlement, project policy, and provider terms at the time of use.
How does the customer recover a degraded connection?
The customer console is designed to present account health, the specific recovery route, and the relevant project context. Operators should follow that route rather than retrying a blind action.
How are events and delivery outcomes represented?
Moira keeps provider outcomes and event references available beside the workflow so a product can distinguish requested, observed, and attention-required states.
What data boundary applies to this provider?
Calendar event state is handled for the selected workspace and product workflow. Moira keeps connection credentials and provider secrets outside public and browser-visible surfaces.
How are webhooks and retries handled?
Event-oriented integrations should retain an identifier, delivery boundary, and retry context. Downstream systems should decide on recovery from evidence instead of replaying an uncertain operation.
What is Moira’s current security and privacy posture?
Moira is progressing through a SOC 2 Type II audit and an ISO 27001 certification program, while operating a GDPR-focused privacy program. These are in-progress initiatives, not completed certifications or a guarantee of suitability for a particular use case.
Where should an engineering team start?
Start by defining project scope, the customer-owned connection path, event contract, and recovery model. Then use the customer console and developer documentation to check live readiness.
Provider path
How the provider path stays operable
A useful integration does not stop at authorization. It makes the current boundary, account state, and recovery route legible inside your product.
Google Calendar workflowIllustrative
- Connect calendar state to a time-bound product action
Use the selected calendar account and visible event state to keep a customer workflow coordinated without hiding ownership.
- See event updates as part of the operating surface
A product can observe configured calendar state changes through a normalized event trail and make an explicit downstream decision.
- Scheduling reconciliation
When projected state and account state need attention, make the recovery action visible before a schedule becomes unreliable.
Start with the right boundary
Connection modes
Calendar consent
Make the calendar account, customer intent, and selected project explicit at the start of the connection journey.
Scheduling scope
Keep a calendar connection tied to the product workflow it serves rather than treating event data as a global workspace resource.
Product workflows
From connection to an operable outcome
Event coordination
Connect calendar state to a time-bound product action
Use the selected calendar account and visible event state to keep a customer workflow coordinated without hiding ownership.- Calendar context retained
- Clear customer intent
- Project-scoped operation
Google Calendar coordination
Connection reviewScoped
Workflow milestoneScoped
Reconciliation windowCheck
State changes
See event updates as part of the operating surface
A product can observe configured calendar state changes through a normalized event trail and make an explicit downstream decision.- Event identifiers
- Webhook evidence
- Traceable processing
Google Calendar event stream
Account state projected
evt_01Event envelope received
evt_02Delivery evidence recorded
evt_03Calendar health
Scheduling reconciliation
When projected state and account state need attention, make the recovery action visible before a schedule becomes unreliable.- Visible reconciliation state
- Reconnect guidance
- Support-ready diagnostics
Google Calendar account Health visible
Connection stateObserved
Project boundaryScoped
Recovery routeReady
Capability boundaries
Capability map
Every category communicates its readiness state in words, not colour alone.
Calendar connection
- Hosted consent presentation
- Project-scoped calendar health
- Reconnection guidance
Scheduling workflows
- Configured calendar actions
- Customer-controlled coordination
- Policy-aware operation
Operational state
- Normalized calendar events
- Reconciliation signals
- Account audit context
Build with context
Developer resources
Keep connection state, event evidence, and security boundaries in the implementation path from the start.
Google Calendar connection architectureStart with project context, the hosted connection route, and an explicit account-health state.Event delivery and recoveryUse signed webhook delivery, event identifiers, retries, and account state to make failures actionable.Connection security boundaryKeep credentials, provider consent, API-key scope, and project isolation separate from browser-visible code.
Data-handling boundaryCalendar event state is handled for the selected workspace and product workflow. Moira keeps connection credentials and provider secrets outside public and browser-visible surfaces.
Architecture questions
Frequently asked questions
How does a Google Calendar connection start?
A workspace member initiates a connection in the intended project context. Moira presents only the authorization path and capability state that the control plane permits.
What happens when calendar consent or scheduling policy changes?
The account health and capability state becomes visible in the customer console. A customer or operator can follow the specific reconnect, approval, or policy-recovery route instead of retrying a blind action.
Is availability guaranteed by this page?
No. This page explains the integration architecture. The live provider registry, workspace policy, and provider terms decide whether a connection or action is available at execution time.
Start with verified readiness