Resend
Send transactional email from your own domains through Resend.
Connect it with: API key. Resend's own documentation: https://resend.com/docs/dashboard/api-keys/introduction.
What agents can do
Connect Resend so the agents working your tasks can reach it. With it connected, they can:
- Send an email from one of your verified domains, with HTML or a React Email template.
- Send a batch of up to 100 emails in one call.
- Check whether a sent email was delivered, opened or bounced.
- List and check the verification of your sending domains.
Before you start
- A Resend account.
- A sending domain added and verified under Domains (resend.com/domains), with the DNS records Resend lists. Until then you can send only from onboarding@resend.dev to your own address.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Resend
Jaah connects to Resend with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- API key: Resend dashboard > API Keys (resend.com/api-keys) > Create API Key. Name it, choose Full access so Test and agents can read your domains, then copy the key: it starts with re_ and Resend shows it only once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Resend card.
- Name the secret and choose who can use it.
- Fill in API key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Resend with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls Resend's API once (GET https://api.resend.com/domains) with the stored values, and shows whether Resend accepted it, or which value Resend refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the Resend secret org/resend”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Resend once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Resend's side too, revoke or delete the key at Resend.
Limitations
- A Sending access key can only send email; Test reads your domains, so it reports such a key as rejected even though sending works.
- Resend limits each team to a few requests per second; a large send should use the batch endpoint.
- Agents can do only what the connected Resend account allows.
Troubleshooting
Test says Resend rejected the API key (401) but the key sends mail
It is a Sending access key. Create a Full access key under API Keys, or keep the sending key if agents only send and ignore the Test result.
Test says Resend rejected the API key (401) or (403)
The key was deleted or mistyped. Create a new key under API Keys (resend.com/api-keys) and select Replace on the secret.
Sending fails with The domain is not verified
Open Domains in Resend, add the DNS records it shows at your DNS provider, and wait for the status to read Verified.
Still stuck? Select Test and read the result: it names the value Resend refused and the status it answered.
FAQ
Can I limit the key to one domain?
Yes, when you create a Sending access key you can pick one domain. Test will then report it rejected, as above.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Resend account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.