# Introduction to Cal.com Atoms (/docs/atoms-deprecated/introduction)

<Callout type="warn">
`@calcom/atoms` is in maintenance mode. Existing integrations keep receiving fixes and new versions on npm, but no new atoms are planned for this package: the next generation of Atoms will be distributed as copy-and-paste components built on coss ui and API v2. Building on your own Cal.com account? Start from [API v2](https://cal.com/docs/api-reference/v2/introduction). Building scheduling into your own product, for your own users? Use [coss.com Scheduling](https://coss.com/products/scheduling).
</Callout>

Cal.com Atoms are customizable React components that let you integrate Cal.com scheduling functionality directly into your application. Using OAuth authentication, your users can connect their Cal.com accounts and manage their scheduling without leaving your app.

## What are atoms? [#what-are-atoms]

Atoms are pre-built UI components that handle:
- **Booking** - Let users book appointments with Cal.com users
- **Availability** - Display and manage availability schedules
- **Event Types** - Create and configure event types
- **Calendar Integration** - Connect Google, Outlook, and Apple calendars
- **Payments** - Accept payments via Stripe for bookings

## Supported frameworks [#supported-frameworks]

Cal.com Atoms currently support:
- **React 18** and **React 19**
- **Next.js 14** and **Next.js 15**

## Prerequisites [#prerequisites]

- An OAuth client created via [OAuth setup](https://cal.com/docs/api-reference/v2/oauth)
- User access tokens obtained through the OAuth flow

## Getting started [#getting-started]

Ready to integrate atoms into your application? Follow our step-by-step setup guide to get started.

<Cards>
  <Card href="/docs/atoms-deprecated/setup" title="Setup Guide">
    Complete installation and configuration instructions
  </Card>
</Cards>

## Authentication flow [#authentication-flow]

Atoms with OAuth work with regular Cal.com user accounts:

1. User clicks "Connect with Cal.com" in your app
2. User authorizes your OAuth client on Cal.com
3. You receive access and refresh tokens
4. Pass the access token to `CalOAuthProvider`
5. Atoms use this token to make API calls on behalf of the user

See the [OAuth documentation](https://cal.com/docs/api-reference/v2/oauth) for details on implementing the authentication flow.
