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

# Connect your app to Ashby

> Connect Ashby to your Lovable app to work with jobs, candidates, applications, and hiring workflows through the Ashby API and Lovable’s connector gateway.

export const connector_0 = "Ashby"

[Ashby](https://www.ashbyhq.com/) is an **applicant tracking** and **recruiting operations** platform. The **Ashby** app connector lets your Lovable app call the [Ashby HTTP API](https://developers.ashbyhq.com/reference) through Lovable’s **connector gateway** using an **API key**, so secrets are not hard-coded in your repository.

With Ashby connected, your app can:

* List and manage **job postings** and **openings**
* Search and view **candidates** and **applications**
* Create and update **candidates** and **applications** programmatically (within API and permission limits)
* Work with **interview** and **pipeline** data where exposed by the API

Ashby is a strong fit when recruiting is centralized in Ashby and you want internal or candidate-facing tools that stay in sync with your ATS.

## Common use cases and example apps

| Example app           | Example prompt                                                                                | Description                                                       |
| :-------------------- | :-------------------------------------------------------------------------------------------- | :---------------------------------------------------------------- |
| **Open roles page**   | *Build a careers page that lists live Ashby jobs with title, location, and apply link.*       | **Public job board** driven by Ashby as the source of truth.      |
| **Referral form**     | *When an employee submits a referral, create or update a candidate in Ashby with their note.* | **Internal referrals** flow into the ATS without manual retyping. |
| **Recruiter console** | *Build a small app that searches candidates by email and shows their current stage.*          | **Fast lookup** for coordinators and recruiters.                  |
| **Interview prep**    | *For a given application ID, show upcoming interviews from Ashby.*                            | **Scheduling context** in one place for hiring managers.          |
| **Pipeline snapshot** | *Show counts of applications by stage for our flagship role.*                                 | **Lightweight analytics** on top of Ashby data.                   |

## How Ashby connections work

* **API key**: You create an API key in Ashby and paste it into Lovable as **API key**. The gateway attaches it to outbound requests; it is not exposed in client-side bundles as plain project text.
* **Gateway**: Traffic goes through Lovable’s **connector gateway**. See [Gateway-based connectors](/integrations/introduction#gateway-based-connectors) for token handling and **per-project request limits**.

<Note>
  **Ashby subscription** limits, API quotas, and feature availability are governed by **Ashby**, not Lovable.
</Note>

## How to connect Ashby

Workspace **admins** and **owners** can connect Ashby.

When a connection is created, link it to the **projects** that should use Ashby.

### Prerequisites

* An **Ashby** account with permission to create **API keys**
* **Lovable workspace admin or owner** role

### Step 1: Create an Ashby API key

1. Sign in to Ashby and open **Admin** (or your organization’s settings area for integrations).
2. Go to **API keys** and create a key with the **minimum scopes** your app needs.

Ashby’s UI entry point: [API keys](https://app.ashbyhq.com/admin/api-keys). For request shapes and endpoints, use [Ashby API reference](https://developers.ashbyhq.com/reference).

### Step 2: Connect Ashby in Lovable

1. Open **Connectors** → **App connectors** and select **Ashby**.
2. Click **Add connection**.
3. Enter a **Display name** (for example `Ashby Production`).
4. Paste the **API key**.
5. Click **Create** / **Save**. Lovable verifies the key against Ashby.

## Limitations

* The connector represents **one** Ashby workspace API key per connection—not each candidate’s or employee’s personal Ashby login.
* **Field-level and workflow rules** inside Ashby still apply; the API cannot bypass Ashby permissions you have not granted to the key.
* **Gateway limits** apply as described in [Gateway-based connectors](/integrations/introduction#gateway-based-connectors).

## How to unlink projects from a {connector_0} connection

Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects.

To unlink projects:

<Steps>
  <Step title="Open Connectors">
    Open **Connectors**, then go to **App connectors**, and select **{connector_0}**.
  </Step>

  <Step title="Open the connection">
    Open the connection you want to manage.
  </Step>

  <Step title="Select projects">
    Under **Linked projects**, check the projects you want to unlink.
  </Step>

  <Step title="Confirm">
    Click **Unlink projects** and confirm.
  </Step>
</Steps>

When unlinked, those projects will no longer have access to {connector_0} through this connection. If a project needs {connector_0} again, you can link it to any available connection.

## How to delete a {connector_0} connection

Workspace admins and owners can delete {connector_0} connections.

<Warning>
  Deleting a connection is permanent and cannot be undone. It will remove the credentials from all linked projects, and any apps using this connection will stop working until a new connection is added.
</Warning>

Before deleting, review the **Linked projects** section to see which projects are currently using the connection.

To delete a connection:

<Steps>
  <Step title="Open Connectors">
    Open **Connectors**, then go to **App connectors**, and select **{connector_0}**.
  </Step>

  <Step title="Open the connection">
    Open the connection you want to remove.
  </Step>

  <Step title="Review linked projects">
    Review the **Linked projects** section.
  </Step>

  <Step title="Delete">
    Under **Delete this connection**, click **Delete** and confirm.
  </Step>
</Steps>