> ## Documentation Index
> Fetch the complete documentation index at: https://docs.automate.ax/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Automate.ax automations are TypeScript programs.
> Use Bun for installation and command examples.
> Use Automate.ax for the product name and automate.ax for the package, CLI, and domain.
> Treat documented public APIs as current; do not invent transitional or deprecated names.

# Get profile

> Retrieves the connected Cal.com profile.

`calcom.getProfile` retrieves the connected Cal.com profile.

```ts automations/get-profile.automation.ts theme={null}
import { automation, markSignificant } from "automate.ax"
import { calcom } from "automate.ax/calcom"

export default automation("Get profile", () => {
  markSignificant(calcom.getProfile({}))
})
```

## Input

This action takes no input.

## Output

Returns an object with these fields:

| Field               | Type             | Required | Description |
| ------------------- | ---------------- | -------- | ----------- |
| `id`                | `number`         | Yes      | —           |
| `username`          | `string`         | Yes      | —           |
| `email`             | `string (email)` | Yes      | —           |
| `name`              | `string \| null` | Yes      | —           |
| `avatarUrl`         | `string \| null` | Yes      | —           |
| `bio`               | `string \| null` | Yes      | —           |
| `timeFormat`        | `number`         | Yes      | —           |
| `defaultScheduleId` | `number \| null` | Yes      | —           |
| `weekStart`         | `string`         | Yes      | —           |
| `timeZone`          | `string`         | Yes      | —           |
| `locale`            | `string \| null` | Yes      | —           |
| `organizationId`    | `number \| null` | Yes      | —           |
| `organization`      | `object`         | No       | —           |

Cal.com enforces account role, plan, and availability requirements. Provider rejections surface as structured action failures with the HTTP status and any `Retry-After` delay.