Skip to content

Gmail

Automate Gmail, and keep the last word on every send

Each new Gmail message can start a workflow: sorted into your own categories, its key details extracted, a reply drafted in the right tone. Nothing leaves your mailbox until you decide — as a draft, after an approval, or sent directly.

Connection
OAuth sign-in
Triggers
1
Actions
5
Sort incoming requests by intent Hover a node to see its role · Drag to move the graph
Email receivedEmail receivedEmail receivedCategorizeCategorizeCategorizeMatchesotherModelMoveMoveMove
Sort incoming requests by intent

What you can automate with Gmail

Triggers

What starts a workflow.

  • Email received

    Starts the workflow when an incoming email matches the conditions.

Actions

What a workflow can do next.

  • Move

    Adds or removes folders/labels on the triggering email, through the mirror (immediately visible in the mailbox).

  • Flag

    Changes the state of the triggering email: read/unread, flagged/unflagged.

  • Compose

    Prepares a message — recipients, subject, body, attachments — without sending anything.

  • Send

    Saves a message as a draft or sends it, from the mailbox of your choice and with the signature of your choice.

  • Read attachments

    Extracts the text of the email attachments (PDF, text, HTML…) into the working data.

Workflows you can build

Each one starts from a real situation and uses only nodes that exist today. Test it on past emails before you publish it.

  • Sort incoming requests by intent

    Every new email is read against the categories you define and filed under the matching label: quotes, support, invoices, the rest.

    1. Email received
    2. Categorize
    3. Move
  • Draft replies to quote requests

    The AI writes a reply in the contact’s tone and language and saves it as a Gmail draft. You read it, adjust it, send it.

    1. Email received
    2. Categorize
    3. Compose (AI)
    4. Send as draft
  • File supplier invoices in Drive

    Invoice attachments land in the supplier’s Google Drive folder, and the email is flagged so the team knows it is done.

    1. Email received
    2. Drive — upload a file
    3. Flag

How to connect Gmail

An administrator registers the Google application once; then each member connects their own mailbox through Google’s consent screen.

Before you start

  • A Gmail or Google Workspace account.
  • An administrator of your Loop & Roll instance registers your organisation’s Google OAuth application once, in a Google Cloud project.
  • An encryption key configured on the instance, to store the tokens.

The full guide in the documentation

  1. An administrator of your Loop & Roll instance registers your organisation’s Google OAuth application once, in a Google Cloud project.
  2. Each member opens Connections, clicks Add a connection, then Connect on the Google card.
  3. Google shows the consent screen: leave every requested access ticked and accept.
  4. The mailbox starts syncing and can be picked in an Email received trigger.

Automate Gmail with Loop & Roll

We build the workflow around your processes, test it on your past emails and put it into service with your teams.