Get Me

Retrieves information about the currently authenticated Calendly user, including profile details, scheduling preferences, and account settings.

Common Properties

• Name - The custom name of the node.
• Color - The custom color of the node.
• Delay Before (sec) - Waits in seconds before executing the node.
• Delay After (sec) - Waits in seconds after executing node.
• Continue On Error - Automation will continue regardless of any error. The default value is false.

info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs

• Client Id - (Optional) The unique client identifier returned by the Connect node. If not provided, you must supply Credentials directly.

Options

• Credentials - (Optional) Calendly API Token credential for direct authentication. Use this if you're not using the Connect/Disconnect pattern.

Output

• Result - An object containing comprehensive user information from the Calendly API, including:
  • User URI and unique identifier
  • Name and email address
  • Scheduling URL (calendly.com/yourname)
  • Timezone preferences
  • Avatar URL
  • Account creation and update timestamps
  • Current role and organization

How It Works

The Get Me node retrieves the profile and settings of the authenticated Calendly user. This is useful for verifying authentication, getting the user's scheduling link, or extracting account details for automation logic.

When executed, the node:

1. Uses either the Client ID from Connect or direct credentials
2. Makes a GET request to the Calendly /users/me endpoint
3. Receives user profile data as a JSON response
4. Parses and outputs the data as an object

Authentication Methods

The node supports two authentication approaches:

Method 1: Using Connect Node (Recommended)

[Connect] -> [Get Me] -> [Disconnect]

The Client ID automatically flows from Connect to Get Me.

Method 2: Direct Credentials

[Get Me with Credentials set]

Provide credentials directly in the node options. No Connect/Disconnect needed.

Response Structure

The Result output contains an object with the following structure:

{
  "resource": {
    "uri": "https://api.calendly.com/users/AAAAAAAAAAAAAAAA",
    "name": "John Doe",
    "slug": "johndoe",
    "email": "john.doe@example.com",
    "scheduling_url": "https://calendly.com/johndoe",
    "timezone": "America/New_York",
    "avatar_url": "https://...",
    "created_at": "2023-01-15T10:30:00.000000Z",
    "updated_at": "2024-11-20T14:25:00.000000Z",
    "current_organization": "https://api.calendly.com/organizations/BBBBBBBBBBBBBBBB"
  }
}

Error Handling

The node will return specific errors in the following cases:

ErrInvalidArg

• Neither Client ID nor Credentials were provided
• Solution: Either use Connect node to get Client ID, or provide Credentials

ErrInternal

• Network error connecting to Calendly API
• API returned an error status (401 Unauthorized, 403 Forbidden, etc.)
• Invalid or expired API token
• Solution: Check network connectivity and credential validity

Usage Examples

Example 1: Verify Authentication

[Start]
  -> [Calendly Connect] (outputs: client_id)
  -> [Get Me] (outputs: result)
  -> [Log] (message: "Authenticated as {{result.resource.name}}")
  -> [Disconnect]
  -> [End]

Example 2: Extract Scheduling URL

[Start]
  -> [Calendly Connect]
  -> [Get Me] (outputs: result)
  -> [Set Variable] (name: scheduling_link, value: {{result.resource.scheduling_url}})
  -> [Send Email] (body: "Book a meeting at {{scheduling_link}}")
  -> [Disconnect]
  -> [End]

Example 3: Direct Credentials (No Connect)

[Start]
  -> [Get Me] (Credentials: calendly_token)
  -> [If] (condition: {{result.resource.email}} == "admin@company.com")
    -> [Run Admin Flow]
  -> [End]

Example 4: Conditional Logic Based on User

[Start]
  -> [Calendly Connect]
  -> [Get Me] (outputs: result)
  -> [If] (condition: {{result.resource.current_organization}})
    -> [List Webhook Subscriptions] (for organization)
  -> [Else]
    -> [Log] (message: "User not part of an organization")
  -> [End]

Usage Notes

• Get Me is useful for testing API connectivity before performing other operations
• The scheduling_url field is the public link users can share for booking meetings
• The user URI is needed for some webhook subscription operations
• Timezone information is useful for scheduling-related automations
• This endpoint doesn't consume significant rate limits (1 request per call)

Best Practices

• Use Get Me to validate credentials at the start of your flow
• Cache user information in variables if needed multiple times in a flow
• Extract the scheduling URL for automated email/SMS campaigns
• Use the timezone field when working with time-sensitive automations
• Check the current_organization field before organization-scoped operations
• Handle authentication errors to prevent flow failures

Common Use Cases

1. Authentication Verification

   • Test if API credentials are valid before running complex workflows

2. Personalized Communications

   • Extract user name and scheduling link for customized messages
   • Send automated booking invitations with the user's Calendly link

3. Multi-User Automations

   • Identify which user's account is being used
   • Route logic based on user role or organization

4. Profile Synchronization

   • Keep external systems updated with Calendly profile changes
   • Sync user data to CRM or database

5. Onboarding Flows

   • Verify new user accounts
   • Extract organization details for team setups

Response Data Usage

Access specific fields in subsequent nodes:

User Name: {{result.resource.name}}
Email: {{result.resource.email}}
Scheduling URL: {{result.resource.scheduling_url}}
Timezone: {{result.resource.timezone}}
User URI: {{result.resource.uri}}
Organization: {{result.resource.current_organization}}

Rate Limiting

Each Get Me call counts as 1 API request against your Calendly rate limit:

• Standard accounts: 100 requests/minute
• Enterprise accounts: Higher limits available

Avoid calling Get Me repeatedly in loops. Cache the result if needed multiple times.