Integrations overview

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

Performance Blocks is the system of record for observations, summaries, and reviews. Integrations extend that system into the surfaces where work actually happens — chat, the browser, your inbox, and your HR system — so the people closest to the work can capture context without changing tabs.

This article gives you the full lay of the land: what each integration does, which feature toggle controls it, who installs it, and a short decision tree for which one to set up first.

Why integrate at all

The single biggest predictor of useful performance reviews is the volume and freshness of observations gathered between formal cycles. Asking managers to remember a quarter of work and write it up in a single sitting produces thin, recency-biased reviews. The integrations exist to make capture frictionless:

• Capture context where work happens. Praise a teammate in Slack, log a customer escalation from your inbox, or tag a deal note from your CRM tab — without leaving the tool.
• Reduce duplicate data entry. Employee names, manager relationships, and departments come from your HRIS. Performance Blocks reflects org changes automatically rather than asking admins to maintain a parallel directory.
• Bring Henry to people, not the other way around. Henry, the AI assistant, lives in the web app — and also in Slack, Teams, the Chrome toolbar, and your email. Each surface is the same Henry, drawing on the same context.

When the integrations are doing their job, observations show up in the system shortly after they happen, summaries deliver to the channel where the team already talks, and admins do not babysit a directory.

The five integrations

Performance Blocks supports five integrations today. Each is opt-in and gated behind a feature flag.

Integration	Feature flag	What it adds
Slack	henryAgentSlack	DM Henry, capture observations from messages, receive summary deliveries in Slack channels.
Microsoft Teams	henryAgentTeams	Chat with Henry in Teams, capture observations from Teams messages, receive summaries.
Chrome extension	henryAgentChrome	Capture observations from any browser tab — CRM tickets, project docs, call transcripts.
Email capture	henryAgentEmail	Forward emails to a per-org Henry inbox so the assistant can extract context and people.
HRIS sync	hrisIntegration	Two-way sync of employees, manager relationships, departments, and termination dates.

Slack, Teams, Chrome, and Email are all surfaces for Henry agent. Each requires the global henryAgentEnabled toggle to be on first, before its surface-specific flag does anything. HRIS sync is independent of Henry and is governed by its own flag.

Plan and feature gating

All five integrations are available only on the Agentic plan. The Team plan covers core performance management — observations, summaries, reviews, blocks — but does not include Henry, HRIS sync, or API access. To upgrade, an org admin can go to Settings → Billing, change the plan, and the feature flags will be made available for configuration immediately on payment success.

Once you are on Agentic, the feature flags are still off by default. An org admin needs to enable them in Settings → Features before any user in the org can connect. The flag layer is there so that you can roll integrations out a surface at a time — for example, turning on Slack first, watching adoption for two weeks, then enabling Teams or Chrome.

The two-flag pattern for Henry surfaces looks like this:

1. henryAgentEnabled — the master toggle for Henry. Required for any Henry surface to function.
2. henryAgentSlack / henryAgentTeams / henryAgentChrome / henryAgentEmail — per-surface toggles.

If henryAgentEnabled is off, the surface toggles are still visible in Settings → Features but greyed out. Enable Henry first, then enable the surfaces you want to roll out.

Who installs what

Different integrations have different installation models, and it is worth being clear about which steps need an admin versus which need every individual user.

Org admin installs

These are one-time installs that an admin does on behalf of the whole org. Once complete, the integration is available to every eligible user.

• Slack — The OAuth app is installed against your Slack workspace by an admin. After install, every Slack user in the workspace can talk to Henry.
• Microsoft Teams — The Teams bot is added through the Teams admin center. Org-wide deployment makes Henry available to every Teams user without further action.
• HRIS sync — The admin authenticates with the HRIS partner (Workday, BambooHR, ADP, or Guidepoint) and configures field mappings. Sync runs centrally on a schedule.
• Email capture — Email capture is enabled per org by an admin. The org's unique Henry email address is generated automatically; users discover it from Settings → Integrations → Email.

Individual user installs

These steps are per-person, even after the admin has enabled the integration org-wide.

• Slack and Teams account linking — Each manager or employee links their personal Slack or Teams account to their Performance Blocks user the first time they DM Henry. Until they link, Henry replies with a one-time link prompt and waits.
• Chrome extension — The extension is installed per-browser-profile from the Chrome Web Store. Each user signs in with their Performance Blocks credentials.
• Sending email captures — Each user sends from a verified work email that matches their Performance Blocks user. Forwarding from an unverified address is rejected.

If you are an admin rolling out a new integration, plan a short message to the team that says, "Henry is now in Slack — DM @henry and follow the link to connect your account." That nudge is the difference between an integration nobody knows about and one people actually use.

Where to manage integrations

All integration configuration lives in one place: Settings → Integrations.

Each integration has its own panel with:

• A status indicator (connected, not connected, error).
• A connect/disconnect button (admin only for org-level connections; user-level for Slack and Teams account links).
• A short summary of what the integration does and what it has done recently.
• Diagnostics for troubleshooting (last sync time, last error, pending events).

For HRIS specifically, you also get a Field mapping view where admins can map their HRIS fields to Performance Blocks fields and a Sync history view that shows the last several scheduled runs with row counts and any errors.

Decision tree: which integration first?

If you are starting from a clean Agentic install and asking, "Which one do I turn on first?" — here is a short decision tree based on what most teams find highest leverage.

Step 1: Are your employee records out of date?

If your team is over about 50 people and your manager hierarchy or department list is stale or partially imported by hand, set up HRIS sync first. Every other integration is more useful when the right people show up in autocomplete and the right manager owns each employee's summary. Spending a week tuning Slack workflows on a stale org chart is wasted effort.

Step 2: Where does your team already talk?

If your team lives in Slack, install the Slack integration second. If you are a Microsoft shop and Teams is where conversations happen, install Microsoft Teams. Pick one — there is no benefit to installing both unless you genuinely have a split workforce.

The chat integration is the highest-leverage Henry surface because it puts capture in the same window as the conversation that triggered the observation. "Praise Jordan for the deck" is a one-line slash command instead of a context switch.

Step 3: Does your team work in browser-heavy tools?

If managers spend most of their day in CRM tools, project trackers, or call-recording dashboards, install the Chrome extension third. The extension lets you capture observations from any tab — a Salesforce opportunity, a Linear issue, a Gong call — without copying URLs into a separate form.

If your team mostly works in native apps (IDEs, design tools), the Chrome extension is lower priority.

Step 4: Do you live in your inbox?

If you find yourself forwarding customer emails to managers with "this is great feedback for X," enable email capture fourth. It turns those forwards into structured observations automatically. If your inbox is mostly internal threads, this one is lower priority.

Step 5: Re-evaluate in 30 days

Integrations are easy to add and easy to remove. After 30 days on whatever you turned on, look at the Insights → Capture sources view to see where observations are actually coming from. If a surface is unused, ask whether it is the wrong surface for your team or whether people just need a reminder it exists.

Security and data handling

Every integration follows the same posture as the rest of Performance Blocks:

• Data stays in your tenant. Slack, Teams, Chrome, email, and HRIS data is scoped to your organization. Performance Blocks does not share observations or employee data across tenants.
• OAuth tokens and API keys are encrypted at rest and rotatable. Disconnecting an integration revokes the token and clears stored credentials.
• Capture is opt-in per page or per message. The Chrome extension only sends data when you click "Capture." The Slack and Teams integrations only act on messages you explicitly route to Henry (DM, mention, slash command, or message action).
• Audit logs record every integration connect, disconnect, and admin configuration change. See Audit logs for what is captured and how long it is retained.

For HRIS specifically, the data classification is higher: termination dates and manager relationships are sensitive. The HRIS partner determines what fields are available; Performance Blocks reads only the fields you map. See HRIS sync for the full field list.

Next steps

• New to Henry? Start with Meet Henry to understand what the assistant does on the web before adding more surfaces.
• Ready to install Slack? See Slack integration.
• Ready to install Teams? See Microsoft Teams integration.
• Browser-heavy team? See Chrome extension.
• Inbox capture? See Email capture.
• Sync from HR? See HRIS sync.

If you are an admin sizing the rollout for your org, the rough effort estimate looks like this:

Integration	Admin effort	Per-user effort	Time to value
Slack	15 minutes	30 seconds	Same day
Teams	30 minutes	30 seconds	Same day
Chrome	None	2 minutes	Same day
Email	5 minutes	None	Same day
HRIS	1–2 hours	None	24 hours (first sync)

The Slack, Teams, Chrome, and Email integrations are designed to be reversible at any time. HRIS, because it writes to the employee directory, deserves a more deliberate rollout — read the HRIS sync article in full before turning it on in production.