fix(slack): add nested profile object to get_user output so users.info-shaped references resolve

[waleedlatif1]

Summary

• Add a nested profile object to the Slack Get User tool output, mirroring Slack's users.info API shape, so references like <block.user.profile.email> resolve instead of throwing InvalidFieldError
• Wire the existing (previously unused) USER_PROFILE_OUTPUT_PROPERTIES schema into USER_OUTPUT_PROPERTIES and add a SlackUserProfile type
• Existing flat fields (user.email, etc.) are unchanged for backward compatibility

Type of Change

• Bug fix

Testing

Typecheck passes with no slack-related errors; block-outputs/block-reference/slack test suites pass (34 tests)

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 10, 2026 9:46pm

[cursor]

PR Summary

Low Risk
Additive response shape and schema metadata only; existing flat user fields are preserved and scope is limited to Get User.

Overview
Fixes Get User Info workflows that reference Slack’s native users.info shape (e.g. user.profile.email) by adding a nested profile object to the slack_get_user tool output and documenting it on the Slack block’s user output.

The slack_get_user transform now populates profile from the API’s user.profile (names, title, contact fields, status, and image_* URLs). USER_OUTPUT_PROPERTIES gains an optional nested profile using the existing USER_PROFILE_OUTPUT_PROPERTIES schema, plus a SlackUserProfile type on SlackUser. Top-level fields like user.email are unchanged.

^{Reviewed by Cursor Bugbot for commit d562353. Configure here.}

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
29606901	Triggered	Generic High Entropy Secret	a54dcbe	apps/sim/providers/utils.test.ts	View secret
32763747	Triggered	Generic Password	3e9849b	helm/sim/tests/validators_test.yaml	View secret
33881454	Triggered	Generic Password	7ffc495	apps/sim/app/api/chat/utils.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[greptile-apps]

Greptile Summary

This PR fixes a InvalidFieldError that occurred when workflows referenced user.profile.email (and similar users.info-shaped paths) on the Slack Get User tool output, by adding a nested profile object that mirrors Slack's API response structure.

• Adds a profile sub-object to transformResponse in get_user.ts, populated with safe ?? '' / ?? null fallbacks for every field, so both flat references (user.email) and nested references (user.profile.email) work correctly.
• Wires the pre-existing (but previously unused) USER_PROFILE_OUTPUT_PROPERTIES schema constant into USER_OUTPUT_PROPERTIES, and adds a SlackUserProfile TypeScript interface with profile?: SlackUserProfile on SlackUser to keep the type system in sync.

Confidence Score: 5/5

Safe to merge — the change is purely additive, all new fields fall back to empty strings or null, and existing flat fields on the output object are untouched.

The change adds a well-scoped nested profile object whose fields are always defensively initialized via ?? '' / ?? null. The USER_PROFILE_OUTPUT_PROPERTIES schema was already defined and validated; it's just now wired in. The SlackUser interface marks profile as optional, which is correct since it is only populated by get_user.ts and not by the list endpoint. No existing behavior is altered.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/tools/slack/get_user.ts	Adds nested profile object to the transformResponse output, mirroring Slack's users.info shape; all fields fall back safely via ?? '' / ?? null.
apps/sim/tools/slack/types.ts	Wires the pre-existing USER_PROFILE_OUTPUT_PROPERTIES into USER_OUTPUT_PROPERTIES, adds SlackUserProfile interface, and adds profile?: SlackUserProfile to SlackUser; backward-compatible and correctly typed.
apps/sim/blocks/blocks/slack.ts	Updates the user output field description to document the newly-added email and nested profile shape.

Sequence Diagram

sequenceDiagram
    participant U as User/Block
    participant T as slackGetUserTool
    participant S as Slack users.info API

    U->>T: userId
    T->>S: "GET /api/users.info?user=<id>"
    S-->>T: "{ ok: true, user: { id, name, ..., profile: { email, display_name, ... } } }"
    T->>T: transformResponse()
    Note over T: Flat fields (user.email, user.display_name, ...)<br/>Nested profile (user.profile.email, user.profile.display_name, ...)
    T-->>U: "{ success: true, output: { user: { ...flatFields, profile: { ...profileFields } } } }"

Loading

_{Reviews (1): Last reviewed commit: "fix(slack): add nested profile object to..." | Re-trigger Greptile}