Published Guides
6
Focused pages with known intent and use-case data.
About Ashby
Ashby combines the features of a CRM, ATS, and scheduler into one snappy platform. It is built for data-driven recruiting. Integrating Ashby allows you to visualize your hiring pipeline in tools like Notion or push real-time interview feedback requests to Slack, keeping the hiring velocity high without the administrative burden.
Integration Capabilities
Ashby has 5 native integrations in its API directory. This page focuses only on guides we publish and maintain.
How Ashby Integrations Usually Work
Start with the implementation model, not the connector. We map each pair by intent so you can decide if native sync is enough or if this workflow needs stronger controls.
Direct Paths
3
Native in at least one direction.
Connector Paths
3
Usually require mapping, retries, or approval gates.
Dominant intent for Ashby: Standard setup (All hub tools (Slack, HubSpot, Sheets, Salesforce) integrate with ALL other tools. These are money pages., offer approval workflow) .
Recommended Build Path for Ashby
These are the only partners recommended on this hub, selected from workflow intent and risk signals. Use one path first, then expand only if your use case truly needs it.
Primary Recommendation: Relay for Approval-Sensitive Workflows
Some high-impact updates should be reviewed before they write into downstream systems, especially for finance, support, and compliance flows.
Relay adds human checkpoints and audit history without slowing every automation down.
Launch Ashby Approval Workflows ->Best for Fast Rollout: Make
3 of this tool's published integration guides require connector logic (field mapping, retries, and conditional routing).
Make is usually the fastest path for teams that need production-ready syncs without writing custom integration code.
Start Ashby Automation in Make ->If your workflow is fully native and low risk, skip paid automation and keep the stack simple.
Common Integration Patterns
- - Hyper-Automation: Users frequently set up 'nudge' automations in Slack for interviewers who haven't submitted feedback within 24 hours.
- - Source Tracking: Deep integration with email (Gmail/Outlook) to track exactly which cold outreach email resulted in a hire.
- - Migration Sync: Often runs in parallel with a legacy ATS (like Lever) during migration, requiring careful data mapping.
Integration Challenges
- - Notification Overload: Because Ashby automates so much, the Slack integration can become noisy if granular preferences aren't set.
- - Calendar Write Access: Ashby requires significant calendar permissions to manage scheduling effectively, which can be a security hurdle for IT.
Before You Integrate
- 1. Audit Calendar Settings: Ensure that 'private' calendar events are not visible to the Ashby scheduler.
- 2. Configure Feedback Reminders: Set up the Slack integration to ping interviewers only during working hours.
- 3. Test Offer Letter Variables: Verify that data from the 'Candidate Profile' correctly populates the dynamic fields in offer letter templates.
Native Integrations from Ashby (3)
These guides cover integrations where Ashby includes a direct native path.
Connector-Based Integrations (3)
These workflows usually need connector logic. Open each setup guide to confirm scope before choosing a platform. If you need a starting point, use the recommendations in the section above.
Other HR Tools
Compare with similar platforms in the hr category.
