Overview
The Get User action retrieves a user by ID and adds it to the workflow context. Use this to access user information for notifications, assignments, or user-related operations.
Configuration
User ID (Required)
The ID of the user to retrieve. The user must belong to a business unit associated with the workflow. Supports variables.
Examples:
{user.id}
{booking.user_id}
{webhook_payload.user_id}Output
Adds a user object to the workflow context with user details:
User ID
Name
Email
Country
Preferred language
Phone
Email verification status
Profile photo URL
Last seen timestamp
Created/updated timestamps
Accessing User Data
After this action, you can access:
{user.id}
{user.name}
{user.email}
{user.phone}
{user.preferred_language}
{user.profile_photo_url}Use Cases
Retrieve user details for notifications
Get user information for assignments
Access user preferences for personalization
Load user data for processing
Examples
1. From Booking
Workflow:
Booking Confirmed trigger
Get User (
{booking.user_id})Send Notification (to user email)
2. From Webhook
Workflow:
Webhook trigger
Get User (
{payload.user_id})Update user preferences
3. Direct User Lookup
Workflow:
Scheduled Time trigger
Get User (
456)Send personalized notification
Best Practices
Verify ID exists - Check user ID before using
Handle not found - Set up error handling for missing users
Check business unit - User must belong to workflow's business unit
Use for personalization - Leverage user preferences and language
Respect privacy - Only access necessary user information