Email capture

Plan availability: This integration is available on the Agentic plan. Team plan customers can upgrade in Settings → Billing.

Email capture turns your inbox into a capture surface for Henry agent. Each Performance Blocks organization gets a unique email address. Forward an email there and Henry extracts the context — who the email is about, what happened, the tone — and creates a draft observation for your review.

This is the right integration for teams who get a lot of relevant signal in email: customer feedback threads, internal recognition notes, escalation chains, vendor escalations, partner kudos.

This article covers how email capture works, common use cases, setting up your org's address, sending captures, the confirmation Henry sends back, security and verification, and the limits you should be aware of.

How email capture works

Each Performance Blocks org has a unique inbound email address generated when email capture is first enabled. The address is owned by Performance Blocks and routes inbound mail through Henry's parser.

When you forward an email to that address:

1. The message is received and matched to your org by the address.
2. The sender's "From" address is checked against your verified work emails. If it matches, the message is accepted; if not, it is rejected with an explanation.
3. Henry parses the email body and extracts:
   • The likely subject of the observation (a person mentioned by name, or the original sender of a forwarded customer email).
   • The substantive content (your forwarding note plus the original email).
   • A sentiment signal (positive, negative, neutral).
   • Any obvious tags (customer name, project name, escalation flag).
4. Henry creates a draft observation in Performance Blocks attributed to you.
5. You receive a confirmation email back with a link to review and finalize the draft.

The observation is a draft until you confirm it from the link in the confirmation email or from the web app. Drafts older than seven days are automatically discarded.

Common use cases

Email capture is most useful for moments that originate in email and would otherwise require you to copy-paste into a separate form.

• Customer feedback emails. A customer writes praising one of your team members. Forward the email; Henry creates a draft observation about that team member with the customer's quote attached.
• Internal recognition. A peer sends a thank-you email about someone on your team. Forward it; Henry captures the recognition with the original sender as the source.
• Escalation threads. A long support thread shows how someone navigated a tough situation. Forward the latest message (Henry follows quoted history); Henry captures the resolution.
• Vendor and partner notes. A partner emails to flag a great working relationship with a member of your team. Forward; Henry captures the relationship.

The common thread is that the email is the original artifact. Email capture lets you preserve it without retyping.

Setup

For admins: enabling email capture

1. Confirm henryAgentEnabled and henryAgentEmail are on in Settings → Features.
2. Go to Settings → Integrations → Email.
3. Click Enable email capture. Performance Blocks generates a unique inbound address for your org.
4. Optionally, click Regenerate if you ever need to rotate the address (the old one stops accepting mail immediately).

The address is shared by everyone in the org — it is not per-user. What gates who can send is the verified-sender check, not knowledge of the address.

For users: finding your address and sending

1. Go to Settings → Integrations → Email in Performance Blocks.
2. Copy your org's Henry inbound email address.
3. Save it as a contact in your email client so it autocompletes (most people name it "Henry" or "Henry capture").
4. Forward any email to that address. Add a brief note at the top if you want to give Henry context — for example, "Praise for Jordan from a key customer."

Sending mechanics:

• Forward is the canonical action — Henry expects the original email as quoted history and your note at the top.
• You can also CC the address on a new email; Henry will treat the email body as the observation content.
• BCC works the same as CC.
• Replying to a previous Henry confirmation does not count as a new capture; use forward or CC for new captures.

Address format and security

The inbound address is a long, randomly generated string at a Performance Blocks domain. It is not guessable. We do not publish the format publicly because the address itself is treated as a low-sensitivity secret — combined with the verified-sender check, it gives a defense-in-depth posture against unauthorized capture.

Two security properties to know:

• Verified sender required. Only emails from a sender address that is verified on a Performance Blocks user record in your org are accepted. Random emails to the address (spam, phishing, mistaken sends) are rejected without creating any observation.
• Address rotation. An admin can regenerate the address from Settings → Integrations → Email. After rotation, the previous address is dead within seconds. Distribute the new address to your team.

If the address ever leaks publicly, the worst-case scenario is rejection emails — anyone outside the verified-sender list cannot create captures. Rotate the address as a precaution.

Confirmations and review

After Henry processes an inbound email, you receive a short confirmation email back at your sender address. The confirmation includes:

• A summary of what Henry extracted (subject person, sentiment, key content).
• A link to Review draft observation in the web app.
• A reject button if Henry got it wrong and you want to discard the draft.

Click the link. The web app opens the draft observation editor with everything Henry parsed pre-filled. Review the subject person, edit the text, attach tags or blocks, and save. Once saved, the observation is real.

If you do nothing, the draft auto-discards after seven days. There is no "auto-save without confirmation" path — every captured observation requires a human review step before it counts.

For confirmations you don't want to receive (high-volume use), the email panel in Settings → Integrations → Email has a per-user toggle for Send capture confirmations. Turn it off; Henry will still create drafts, you just won't get the email.

What Henry extracts

When Henry parses an inbound email, it tries to identify:

Extracted field	Example
Subject person	"Jordan Park" — the person the email is about, not the sender
Source person	The original sender if forwarded (e.g., the customer)
Body content	A clean version of your note plus the relevant original text
Sentiment	Positive, negative, neutral
Tags	Project name, customer name, "escalation" flag if present
Quoted history	Preserved as context but not duplicated in the observation

These are all best-effort guesses, surfaced for you to confirm or correct. Henry never fabricates a person — if no name is recognizable, it leaves the subject blank and asks you to choose during review.

Limitations

A few things email capture does not do, on purpose or by limitation.

• One email at a time. Each forwarded email becomes one draft observation. To capture multiple people from one email, save the draft for one person, then re-forward the same email and choose the second person on review.
• Large attachments are dropped. Inline images and small attachments are kept; attachments larger than a few megabytes are stripped. The email body is always preserved.
• Only your verified work email is accepted. If you send from a personal account, an unverified alias, or an email-on-behalf-of arrangement, the message is rejected. Verify additional sender addresses on your user profile if you legitimately need to send from more than one.
• No background email subscriptions. Email capture does not subscribe to a shared mailbox or scrape a folder. You forward what you want captured; nothing is captured passively.
• Encrypted email is not supported. S/MIME and PGP-encrypted bodies cannot be parsed. Forward the decrypted plaintext if needed.
• Reply chains beyond a few levels deep. If you forward an email with a very long quoted history, Henry trims the quoted text to the most recent few messages to keep the parse focused.

Disabling email capture

To disable per user, turn off Send capture confirmations in Settings → Integrations → Email if you simply want to stop receiving confirmations.

To disable for the whole org, an admin can:

1. Go to Settings → Integrations → Email.
2. Click Disable email capture.
3. The inbound address is decommissioned. Future emails to that address bounce.

Existing observations created via email capture remain. Disabling stops future captures only.

To rotate the address (without disabling):

1. Go to Settings → Integrations → Email.
2. Click Regenerate address.
3. The old address bounces immediately; the new one is active.

Troubleshooting

"I forwarded an email and got nothing back"

Check:

• The address you sent to. A typo means the message went nowhere (or to a stranger). Re-copy from Settings → Integrations → Email.
• The sender address. Did you send from a verified work email? Check Settings → My account for verified emails.
• Your spam folder. Henry's confirmation email may have been routed by your spam filter.
• The email panel diagnostics view. It shows your recent inbound attempts and the result for each.

"Henry rejected the email"

The confirmation explains why. Common reasons:

• Sender not verified.
• Address invalid (was rotated by an admin).
• Email was empty or unparseable.
• Email was encrypted.

"The draft has the wrong person"

This is expected for some emails — Henry's guess is best-effort. Open the draft from the confirmation link and choose the right person manually. Save.

"I'm getting too many confirmations"

Turn off Send capture confirmations in Settings → Integrations → Email. Drafts will still be created; you just won't be emailed.

"I want to forward from a shared mailbox"

Shared mailboxes generally won't pass the verified-sender check because the From address isn't tied to a single user. The supported pattern is to forward from your individual account, not the shared mailbox.

Related

• Meet Henry
• Chrome extension
• Integrations overview