Integration · Email and identity

attendo + Google Workspace

Your customers’ email comes into attendo and turns into documents, and replies go out from the right mailbox. With Google Meet, appointments show up in Google Calendar, and your team signs in with their Google account.

Status Available

Request a demo See what travels

Gmail and Google Workspace
Many mailboxes with one service account
Sign-in with Google

attendo Google Workspace

from Google Workspace to attendo Email from your mailboxes Each email creates or continues a document
from attendo to Google Workspace Replies from the mailbox or alias With their delivery status
from attendo to Google Workspace Google Calendar appointments With the Meet meeting if it is online

What it solves

The service mailbox, answered by hand from Gmail

Many service companies run on Google Workspace. Their service mailbox receives requests that are answered from Gmail, by hand and with no record. Nobody knows which customer wrote three times this week or who answered.

With Google connected, email comes into attendo, becomes a document with its customer identified, and replies go out from the document with the mailbox address.

What it does

What it does, piece by piece

Email, appointments, meetings and sign-in, each with the connection it needs.

Three ways to connect a mailbox

With each person’s authorization (OAuth), with a service account for every mailbox in the domain, or with an app password.

Email that becomes a document

Each email creates or continues a document. With the Gmail API, labels work as folders and send-as aliases are recognized automatically.

Inbound email within seconds

Gmail notifies attendo through Google Cloud and the document is created within seconds. The periodic check keeps running underneath as a safety net.

Google Calendar appointments

attendo reads the availability of people and rooms, offers only free slots and creates the event with its Meet meeting.

Google Meet meetings

The video call is created from the document, with its link, and the record keeps who attended and how long it lasted.

Sign in with Google

Your team signs in with their Google account, in the mobile app too, and attendo still asks for their two-factor code if they have it turned on.

What travels

What travels, and in which direction

Without instant inbound email, attendo checks each mailbox every 5 minutes, or as often as you choose.

What travels between attendo and Google Workspace, in which direction and when
Data	Direction	When
Incoming emails, with their attachments	Directionfrom Google Workspace to attendo	WhenWithin seconds with instant inbound email
Replies and emails from attendo	Directionfrom attendo to Google Workspace	WhenOn send, or in the background with retries
Read, trash and spam	Directionfrom attendo to Google Workspace	WhenWhen you do it in attendo
Availability of people and rooms	Directionfrom Google Workspace to attendo	WhenWhen the slots for an appointment are calculated
Appointment event, with its Meet meeting	Directionfrom attendo to Google Workspace	WhenWhen it is confirmed, changed or canceled
Meeting attendees and duration	Directionfrom Google Workspace to attendo	WhenWhen the meeting ends
Identity: the email address	Directionfrom Google Workspace to attendo	WhenAt each sign-in

Getting started

How to get started

It is set up in Settings. The first setup is done with you, using your organization’s Google Cloud project.

Status Available

What you need

A Google Cloud project owned by your organization, with the Gmail API and the consent screen
For several Workspace mailboxes, a service account with domain-wide delegation
For instant inbound email, Cloud Pub/Sub and a verified domain
For appointments and meetings, Google Workspace with the Calendar and Meet APIs

Typical effort. Half a day with your Google administrator the first time. The Google Cloud project and domain-wide delegation take the most effort, and they are done in Google.

Step 1
Google Cloud project

Your administrator enables the Gmail API, sets up the consent screen and the client ID, and authorizes your instance’s redirect address.
Step 2
Mailboxes in attendo

You choose the connection mode and connect each mailbox. Testing the connection shows Google’s exact error before you save.
Step 3
Each mailbox, to its queue

Who can send, inbound or outbound, aliases and the flows that turn email into documents.
Step 4
The optional parts

Instant inbound email, Google Calendar appointments, Meet meetings and sign-in with Google.

Honesty

What it does not do

Google Drive
It does not use it for document management: attachments are stored with the document.
Google Contacts
It does not sync Google contacts with attendo customers.
Changes made in Google Calendar
If someone moves the appointment in Calendar, attendo does not pick it up: the appointment is changed from attendo.
Meetings with free Gmail
Meet meetings from the document need Google Workspace with domain-wide delegation.

Keep going

What goes with it

All integrations Every connection, with its real status.

Frequently asked questions

Does it work with free Gmail?

Email does, with OAuth or an app password. Meet meetings from the document need Google Workspace.

Why do we need a Google Cloud project?

Because attendo connects with your organization’s credentials, not with a shared app. Access control stays within your company.

Can I read other people’s mailboxes in the domain?

Yes, with the service account and domain-wide delegation, the equivalent of Microsoft shared mailboxes.

Do appointments show up in my Google Calendar?

Yes, with Google Meet connected and calendar permission. They are created in the calendar of the person handling them.

Do I lose email if instant inbound email fails?

No. The periodic check keeps running underneath: at worst, it takes as long as it would without it.

Cookie settings