Integrations · Ashby
A Guild agent can search candidates, move applications through hiring stages, schedule interviews, and manage offers in Ashby. Guild stores the API key server-side and injects it through the credential proxy, so the key never appears in agent code or prompts. Credential policies let you restrict which Ashby operations each agent can call.
Book a demo
See how teams govern agents that use Ashby.
Start free
Connect Ashby and scope your first agent.
What the Ashby integration exposes
The tools cover candidates, applications, jobs, openings, interview plans and schedules, offers, approvals, feedback forms, surveys, custom fields, departments, locations, and users. Read operations fetch lists and individual records; write operations create, update, transfer, and archive them. Tools for hiring team membership, interviewer pools, and source tracking are also included.How it works
1
Create an Ashby API key
In Ashby, go to Admin > API Keys and create a key with the permissions your agent needs.
2
Encode the key
Run the base64 command shown on the integration page, appending a colon to the key before encoding. The trailing colon marks the empty password that Ashby Basic auth requires.
3
Connect the credential in Guild
In Guild, go to Access & setup > Credentials, click Connect, select ashby, and paste the encoded output into API Key. See Credentials for workspace, member, and agent-scoped options.
Why Ashby access needs governing
Ashby holds sensitive hiring data: candidate profiles, compensation in offers, fraud check results, and feedback scorecards. An agent with an unconstrained credential can read or write any of that data. Credential policies let you write ALLOW and DENY rules that Guild’s proxy enforces before any request reaches Ashby, limiting an agent to the specific operations it needs, such as read-only candidate search or stage changes only. Guild stores the API key server-side and injects it after the policy check passes. Agent code, prompts, and container environments never see the key. You can scope a credential to one workspace, one member, or a single agent using the options described in Credentials, and every call is logged so you can audit what each agent did.About the Ashby integration
The Ashby integration gives agents the Ashby API: candidates, applications, jobs and openings, interview plans and schedules, offers, feedback, and custom fields. The integration isguildlabs~ashby.
Authentication
- Type: API key, sent as HTTP Basic authentication
Authorization: Basic <value>, so enter the key followed by a colon, base64-encoded:
Setup
1
Create an API key
In Ashby, go to Admin > API Keys and create a key with the permissions your agent needs.
2
Encode it
Run the command above with the key.
3
Connect Ashby
In Guild, go to Access & setup > Credentials, click Connect, select ashby, and paste the output into API Key.
Usage
Selecting specific tools
Tools are named with theashby_ prefix and a _v2 suffix. The integration has 160 tools, so use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildlabs~ashby:
All 160 tools
All 160 tools
Frequently asked questions
Can I limit an agent to reading candidates without letting it change applications?
Can I limit an agent to reading candidates without letting it change applications?
Yes. Credential policies support ALLOW rules scoped to specific operations. You can allow operations like ashby_candidate_search_v2 and ashby_candidate_info_v2 while adding a DENY rule for ashby_application_change_stage_v2 and other write operations.
Does the integration receive Ashby webhook events?
Does the integration receive Ashby webhook events?
Not yet. The catalog entry lists no webhook events for this integration, so agents cannot be triggered by Ashby events through Guild’s event trigger system.
Can different agents use different Ashby accounts?
Can different agents use different Ashby accounts?
Yes. You can connect credentials at the workspace, member, or agent scope. Dedicating a credential to one installed agent means that agent uses its own Ashby API key while other agents use a separate account-level credential. See Credentials for how Guild resolves which credential to use.
Do I need to include all the tools or can I pick a subset?
Do I need to include all the tools or can I pick a subset?
You can pick a subset. The SDK’s pick() function lets you spread only the named tools into your agent’s tools object, which keeps the model’s tool list focused on the task at hand.
Put a governed agent on your Ashby hiring pipeline today
Book a demo
See how teams govern agents that use Ashby.
Start free
Connect Ashby and scope your first agent.