Invoice email

Two ways to send

The rest of this page covers the first path: bringing your own Resend account.

Set up your own Resend account

1. Create a Resend account

Sign up at resend.com. The free tier is enough for invoicing.

2. Verify your sending domain

In Resend, open Domains and add the domain you invoice from. Resend shows the DNS records to add at your registrar:

Verification usually completes within minutes, but DNS can take up to a day to propagate. Until the domain is verified you can only send to the email address on your own Resend account — client sends will be rejected.

3. Create an API key

Go to resend.com/api-keys and create a key with Sending access — that's all invoice email needs. Copy it now; Resend only shows it once. Keys start with re_.

4. Give the key to getScribe

Desktop app: open Settings → Email and paste the key into Resend API Key, then save. It's stored locally on that device and masked whenever it's read back.

CLI: set it in the environment, or add it to ~/.scribe/config.json under email.resendApiKey:

export RESEND_API_KEY=re_xxxxxxxxxxxx

{
  "email": {
    "resendApiKey": "re_xxxxxxxxxxxx",
    "defaultFrom": "invoices@yourdomain.com"
  }
}

5. Set the address you send from

The desktop app sends from the company email on your invoice template. If that's empty it falls back to invoices@resend.dev, Resend's shared test sender, which only delivers to your own Resend account address — so a client would never receive the invoice. Set a company email on the domain you just verified. The CLI uses email.defaultFrom from ~/.scribe/config.json the same way.

Send an invoice

Desktop app: open the invoice and press Send. With a key configured it goes out through your Resend account; without one, getScribe offers to send it for you instead.

CLI:

scribe invoice send <number-or-id> [--to email] [--cc email]

With no --to, the invoice goes to the client's email. Set one with scribe client update <name> --email <email>. A successful send marks the invoice as sent.

What bring-your-own means

• Your account. Deliverability, sending limits, and reputation are yours. getScribe never sees or proxies the message.
• One device. The desktop key lives in that install's local settings and is not synced to the hub, so each machine you invoice from needs its own key (or its own ~/.scribe/config.json entry).
• One sender. The key belongs to a single Resend account, so it can't be shared across a team the way managed send can.

Troubleshooting

"No Email API Key Configured" in the desktop app

No Resend key is saved on this device. Add one under Settings → Email (step 4 above), or choose Send from invoicing@getscribe.ai to send through getScribe on a paid plan.

"RESEND_API_KEY not configured" from the CLI

The CLI reads RESEND_API_KEY from the environment first, then email.resendApiKey in ~/.scribe/config.json. A key saved in the desktop app's settings is not visible to the CLI — set it in one of those two places.

The send is rejected as an unverified domain

Resend only accepts a from-address on a domain you've verified. Confirm the domain shows Verified in Resend, and that the address you send from is on that exact domain — a subdomain, or a different domain you also own, has to be verified separately.

The key is rejected (401)

The key was revoked, mistyped, or copied with trailing whitespace. Generate a fresh key with sending access and paste it again. Domain- restricted keys only work for the domain they're scoped to.

Invoices land in spam

Add a DMARC record if you skipped it, and send from a real human-looking address on your invoicing domain rather than a brand-new one. A domain with no sending history is treated with suspicion at first — reputation builds as clients receive and open your invoices.