Get User: Slack action · Tiny Command

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
User ID user	string	Required	Slack user ID (starts with U or W). Find via List Users. Not the username or display name.

Sample request

{
  "user": "U1234567890"
}

Returns

{
  "ok": true,
  "user": {
    "id": "U1234567890",
    "name": "john",
    "profile": {
      "email": "john@company.com",
      "image_72": "https://avatars.slack-edge.com/...",
      "status_text": "Working remotely",
      "display_name": "John"
    },
    "is_admin": false,
    "real_name": "John Doe"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get User.

What does the Get User action do in Slack?

Retrieves detailed profile information for a Slack user (real_name, display_name, email, timezone, custom fields). Used to enrich a message trigger with the sender's identity.

What inputs does Get User require?

Required: User ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Slack returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get User support batch operations?

Yes. Run Get User inside a Loop node to process arrays. Tiny Command handles Slack's rate limits automatically so you don't have to throttle manually.

More actions