Skip to content

feat(slack): add tool to look up a user by email#201

Merged
daltoniam merged 2 commits into
mainfrom
feat/slack-lookup-user-by-email
Jul 8, 2026
Merged

feat(slack): add tool to look up a user by email#201
daltoniam merged 2 commits into
mainfrom
feat/slack-lookup-user-by-email

Conversation

@daltoniam

Copy link
Copy Markdown
Owner

Why

Automated agents (e.g. Curri's Live Delivery triage bot) often know only an internal user's email address and want to @-mention that person in Slack. Today the only way to map an email to a Slack user is slack_list_users, which pages the entire workspace and filters client-side — slow and awkward for a single lookup.

What

  • New slack_lookup_user_by_email tool wrapping Slack's users.lookupByEmail.
  • Returns the Slack user ID plus a ready-to-use mention string (<@U…>) so callers can tag the user directly.
  • Requires the bot token to have the users:read.email scope (documented in the tool description).

Test

  • go build, go vet, and go test ./integrations/slack/ all pass.

💘 Generated with Crush

daltoniam added 2 commits July 8, 2026 17:18
Callers that only know an internal user's email address had to page the
entire workspace to find their Slack account, which is slow and awkward
for automated agents that want to @-mention the right person.

Add a direct email-to-user lookup that returns the Slack user ID and a
ready-to-use mention string, so an agent can tag someone from just their
email in a single call.
The security scan started failing on newly published advisories: a
crypto/tls issue fixed in the latest Go patch release, and two AWS SDK
service advisories. None are related to this branch's feature work, but
they block the pipeline.

Move to the patched Go release and update the affected AWS SDK
dependencies so the vulnerability scan passes cleanly.
@daltoniam daltoniam merged commit 3ec88a0 into main Jul 8, 2026
5 checks passed
@daltoniam daltoniam deleted the feat/slack-lookup-user-by-email branch July 8, 2026 22:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant