- 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
Common use cases and example apps
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 for token handling and per-project request limits.
Ashby subscription limits, API quotas, and feature availability are governed by Ashby, not Lovable.
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
- Sign in to Ashby and open Admin (or your organization’s settings area for integrations).
- Go to API keys and create a key with the minimum scopes your app needs.
Step 2: Connect Ashby in Lovable
- Open Connectors and select Ashby.
- Click Add connection.
- Enter a Display name (for example
Ashby Production). - Paste the API key.
- 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.
Manage your connection
Connections are managed from Connectors: select , then open the connection.- Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
- Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.