sumwerk

Docs Guide · updated September 20, 2026

Send from your own Google mailbox

Emails you write in sumwerk, and the ones your automations and sequences send in your name, can go out from your own Google Workspace mailbox. They then sit in your Sent folder, come from your address, and a reply is an ordinary conversation in your inbox.

sumwerk asks Google for permission to send, and nothing else. It cannot read, search or delete mail. That is also why a sequence cannot notice a reply: every email carries an unsubscribe link instead.

Without this setup everything still works: emails go out as “Your Name via sumwerk”, with replies going to you.

What you need

  • A Google Workspace (the company kind of Google account), and someone who may create a project in Google Cloud for it. Usually a Workspace administrator.
  • To be an owner of your sumwerk account.
  • About ten minutes. It is done once per company; after that every colleague connects their own mailbox with two clicks.

Because the app you create is internal to your own Workspace, Google does not review it, and only people of your company can ever use it.

1. Create a project

Open console.cloud.google.com, signed in with your company account. In the project picker at the top choose New project. Name it sumwerk, and make sure Organisation shows your company’s domain. Create it and select it.

2. Switch on the Gmail API

Menu → APIs & ServicesLibrary. Search for Gmail API, open it, press Enable.

Menu → APIs & ServicesOAuth consent screen (in newer consoles: Google Auth PlatformBranding and Audience).

  • App name: sumwerk. Support email and developer contact: your address.
  • User type / Audience: Internal. This is the step that makes a review unnecessary.
  • Scopes / Data accessAdd or remove scopes → add these three and save:
    • https://www.googleapis.com/auth/gmail.send (send email on your behalf)
    • openid
    • email (so sumwerk knows which address it sends from)

4. Create the client

Menu → APIs & ServicesCredentials (newer consoles: Google Auth PlatformClients) → Create credentialsOAuth client ID.

  • Application type: Web application. Name: sumwerk.
  • Authorised redirect URIs → add exactly the address sumwerk shows you under Account → Email → “Your company’s Google app”. For sumwerk.com it is:
https://www.sumwerk.com/mailbox/callback

Press Create. Google shows a Client ID and a Client secret. Keep the window open.

5. Enter both values in sumwerk

In sumwerk: Account → Email → Your company’s Google app. Paste the Client ID and the Client secret, press Save Google app. The secret is stored encrypted and never shown again; to replace it, paste a new one.

6. Everyone connects their mailbox

Each colleague, once: Account → Email → Connect my Google mailbox. Google asks whether sumwerk may send email on your behalf. Allow it. From then on their emails go out from their own address, and the page says so.

Checking that it works

Open a customer, Write an email, send one to yourself. It should arrive from your own address, and the timeline shows “sent from you@yourcompany.com”. If it says “via sumwerk” instead, the mailbox is not connected for the person who sent it.

If something goes wrong

What you see Why, and what to do
Google says “Access blocked: this app’s request is invalid” or redirect_uri_mismatch The redirect URI at Google differs from the one sumwerk shows. It has to match to the letter, including https:// and www.
Google says “Access blocked: … can only be used within its organisation” You are signed in to Google with an account outside your Workspace (a private Gmail address). Switch to your company account
sumwerk says “Google did not accept the sign-in” Client ID and secret do not belong together, or the secret was replaced at Google. Paste both again
An email is marked failed: “the Google mailbox … has to be connected again” The permission was withdrawn (password change, an administrator’s policy, or you removed it). Connect the mailbox again
Emails arrive, but from “… via sumwerk” That colleague has not connected their mailbox yet, or an automation sends in the name of someone who has not

Taking the permission back

  • One person: Account → Email → Disconnect, and at Google under myaccount.google.com/permissions remove sumwerk.
  • The whole company: delete the client in Google Cloud. Every connection stops working at once.

Connect Stripe and check your own numbers

A restricted, read-only key is all it takes. The first import runs in a few minutes; every number you see opens into the customers and Stripe references behind it.

Start free