Mailbox consent
Separate provider consent from Moira API credentials and show the account owner the exact mailbox path being connected.
Mailbox connection architecture
Design mailbox consent, event state, and recovery as one product journey.
Connect a customer-authorized mailbox to a named project and keep account health, message state, and recovery information where the team can act on it.
Email connection architecture
Set up Gmail 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.
Project-isolated mailbox
Attach the mailbox state to the intended workspace and project so it cannot silently bleed into another customer workflow.
The product workflow
Gmail 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 Gmail.
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
Gmail 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 Gmail 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 Gmail 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 Gmail a visible, policy-aware stage in a controlled multi-step outreach workflow.
Explore use caseDeveloper integration
Make the Gmail 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: "gmail",
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
Gmail integration FAQ
Answers describe product boundaries and operational recovery without making provider capability promises.
How does a Gmail 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 Gmail 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?
Mailbox data is handled only in the selected customer workflow and project boundary. Browser clients do not receive provider credentials, service tokens, or raw connection secrets.
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.
Gmail workflowIllustrative
- Represent mailbox state in the product context that needs it
Show a customer which connected mailbox is healthy, needs attention, or has a pending consent/recovery action.
- Make inbound and outbound context observable
Carry normalized mailbox events and account context into the workflow without presenting every provider behavior as identical.
- Turn token expiry into a clear customer action
Explain whether a mailbox needs reconnection, consent review, or support intervention before a team loses time on blind retries.
Start with the right boundary
Connection modes
Mailbox consent
Separate provider consent from Moira API credentials and show the account owner the exact mailbox path being connected.
Project-isolated mailbox
Attach the mailbox state to the intended workspace and project so it cannot silently bleed into another customer workflow.
Product workflows
From connection to an operable outcome
Mailbox projection
Represent mailbox state in the product context that needs it
Show a customer which connected mailbox is healthy, needs attention, or has a pending consent/recovery action.- Mailbox ownership visible
- Actionable health state
- Clear support context
Gmail account Health visible
Connection stateObserved
Project boundaryScoped
Recovery routeReady
Thread and event flow
Make inbound and outbound context observable
Carry normalized mailbox events and account context into the workflow without presenting every provider behavior as identical.- Event references
- Project-aware messages
- Delivery diagnostics
GmailContextEvents
01
Connected account context attached
02
Workflow event ready for review
03
Recovery state is visible
Connection recovery
Turn token expiry into a clear customer action
Explain whether a mailbox needs reconnection, consent review, or support intervention before a team loses time on blind retries.- Specific recovery route
- Visible status history
- No secret exposure
Gmail event stream
Account state projected
evt_01Event envelope received
evt_02Delivery evidence recorded
evt_03Capability boundaries
Capability map
Every category communicates its readiness state in words, not colour alone.
Mailbox operations
- Hosted consent state
- Project-isolated account health
- Recovery instructions
Email workflows
- Customer-authorized message paths
- Provider-aware account state
- Configured action boundaries
Event evidence
- Normalized mailbox events
- Signed webhook delivery
- Traceable account context
Build with context
Developer resources
Keep connection state, event evidence, and security boundaries in the implementation path from the start.
Gmail 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 boundaryMailbox data is handled only in the selected customer workflow and project boundary. Browser clients do not receive provider credentials, service tokens, or raw connection secrets.
Architecture questions
Frequently asked questions
How does a Gmail 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 mailbox consent or connection health 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