A shared place for client mail
The planned Gmail connection brings the workspace mailbox into Inbox. People with Inbox access can follow the conversation and the work behind a reply.
Google WorkspaceComing soon
From the client email to the next meeting.
Gmail conversations, Google Calendar events and Meet links, connected to client work.
Join early accessExplore the plan. Live connection is not available yet.Workflow preview · Coming soon
Google WorkspaceClient email in Gmail
Tamaam workspaceSample workflowConversation linked to a client
Client email in GmailContext from Google Workspace
09:41Linked to Brand launchThe conversation stays with the project
Next step beside the projectContext ready for your next decision
Illustrative workflow. Live connections coming soon.
Where the connection fits.
Calendar context alongside delivery
Google Calendar is a planned provider. The aim is to keep availability and bookings connected to the relationship, with Google Meet links for meetings.
Context for a considered reply
Nefer is designed to read linked work and prepare drafts for review. Connecting a mailbox does not authorize every teammate to read mail or permit a draft to send itself.
What to prepare.
A practical checklist before a live connection becomes available.
- Choose the shared mailbox your workspace will use.
- Identify who should have Inbox access.
- Confirm the calendar and time zone for bookings.
- Review provider permissions before granting access.
What to know today.
- Live Gmail and Google Calendar syncing are not available in the current preview.
- One shared synced mailbox per workspace is the current product direction.
- Historical import, sync frequency and exact scopes will be documented before release.
Before you connect.
Can I connect Google Workspace now?
No. Connections are in development. These pages describe planned workflows, not integrations you can connect in the current preview. Early access lets you follow the product’s progress; it does not activate this connection or start a paid subscription.
Which permissions will it need?
Exact provider permissions and supported account types will be published after implementation and verification. Review them before granting access. This preview does not request permissions or connect an account.
Will a connection let Nefer act automatically?
Tamaam’s product principle is that Nefer proposes and a person approves. A provider connection is not permission to silently send messages or change your work.
See the work around
the connection.
A provider is one part of the workflow. Explore the module, learn the method and follow related connection plans.
Provider names and marks identify planned compatibility, not partnership or endorsement.