Aura Auth

ClickUp

Add ClickUp authorization provider to Aura Auth for authentication and authorization

ClickUp OAuth App

Register the Application

The first step is to create and register an OAuth App on the ClickUp Workspace to obtain access to the user's resources.

  1. Navigate to your Clickup Avatar and go to Settings > Integrations & ClickApps > ClickUp API > ClickUp API Settings.
  2. Click Create an App.
  3. Fill in the "App name".
  4. Set the Redirect URL(s) to http://localhost:3000/auth/callback/click-up.
    • (Make sure to replace http://localhost:3000 with your production domain when deploying)
  5. Click Create App.
  6. Ensure you copy the Client ID and click Generate a new client secret.

Installation

Install the @aura-stack/auth package. Please follow the Installation Guide to complete the setup and core configuration for aura-stack/auth.

npm install @aura-stack/auth

Environment setup

Now, you must configure the environment variables required by Aura Auth, including the ClickUp credentials and the encryption secrets.

.env
# Aura Secrets
AURA_AUTH_SECRET="your-32-byte-secret"
AURA_AUTH_SALT="your-32-byte-salt"

# ClickUp Credentials
AURA_AUTH_CLICK_UP_CLIENT_ID="your_click_up_client_id"
AURA_AUTH_CLICK_UP_CLIENT_SECRET="your_click_up_client_secret"

Configure the Auth Instance

Configure the createAuth instance inside an auth.ts file located at the root of your project. Ensure you explicitly export the handlers, api, and jose objects.

@/lib/auth.ts
import { createAuth } from "@aura-stack/auth"

export const auth = createAuth({
  oauth: ["click-up"],
})

// Extract the required utilities
export const { handlers, api, jose } = auth

The handlers object contains mapping utilities for standard HTTP methods (GET, POST, PATCH) as well as a unified ALL handler. This allows you to easily mount the authentication routes across any framework (Next.js, Elysia, Express, etc.).

Customizing the OAuth Provider

If you need to define custom scopes, change the response type, or map profile data differently, you can use the provider's factory function instead of a simple string identifier.

@/lib/auth.ts
import { createAuth } from "@aura-stack/auth"
import { clickUp } from "@aura-stack/auth/oauth/click-up"

export const auth = createAuth({
  oauth: [
    clickUp({
      authorize: {
        params: {
          clientId: process.env.AURA_AUTH_CLICK_UP_CLIENT_ID!,
        },
      },
    }),
  ],
})

export const { handlers, api, jose } = auth

Sign In to ClickUp (Client & Server)

There are multiple ways to trigger the sign-in flow depending on your ecosystem.

Sign-in Path (Direct Navigation)

The common route to trigger the auth flow natively without needing a client library is simply navigating the browser to: http://localhost:3000/auth/signIn/click-up


Client-Side (React, Vue, etc.)

You can utilize the createAuthClient utility to programmatically trigger sign-ins. You can also define a redirectTo destination.

Constraint Rule: The baseURL passed into createAuthClient MUST exactly match the root domain and path where the HTTP handlers expose their endpoints on the server.

components/Login.tsx
import { createAuthClient } from "@aura-stack/auth/client"

export const authClient = createAuthClient({
  baseURL: "http://localhost:3000/auth",
})

const triggerSignIn = async () => {
  await authClient.signIn("click-up", {
    redirectTo: "/dashboard",
  })
}

Server-Side (Next.js Actions, Remix Loaders, etc.)

For environments supporting server-side actions, use the programmatic api.signIn method securely.

actions.ts
import { api } from "./auth"

export const serverSignIn = async () => {
  const response = await api.signIn("click-up", {
    redirectTo: "http://localhost:3000/dashboard",
  })

  // Example returning redirect location
  return response.headers.get("Location")
}

Session Retrieval

After a user successfully signs in, you can retrieve their session data securely.

Client-Side:

const session = await authClient.getSession()
console.log(session?.user) // The authenticated ClickUp user profile

Server-Side:

// Note: You must pass the native Web Request object or Headers!
const session = await api.getSession(request)
console.log(session?.user) // Safely retrieved backend session

Resources

On this page