Ashby
Ashby modern ATS candidate management
Ashby is the modern ATS popular with high-growth startups and tech companies that wanted Greenhouse-class structure with better UX, deeper analytics, and a more API-friendly platform. Tiny Command exposes three actions, no triggers (Ashby supports webhooks configured per-event in admin Settings → Webhooks; point at a Tiny Command webhook trigger URL for candidate-created, application-stage-changed events): List Candidates (paginated with filters by source, stage, recently active), List Jobs (open requisitions with filters), Create Candidate (push a sourced candidate into Ashby with name, email, optional initial application against a job, source attribution). The connection uses an Ashby API key from Admin → API keys. Ashby's data model is heavy on candidate-application-interview relationships — a Candidate can have multiple Applications (one per job they applied to), each Application has Interview Schedules and Scorecards. The typed action surface covers the core sourcing-to-pipeline path; deeper interview-management and analytics workflows reach via HTTP action.
Do anything Ashby can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Candidate | Creates a new candidate with name, email, optional initial application against a job, and source attribution. The standard hook for "sourced via LinkedIn or Sales Navigator → push to Ashby with the right source for sourcing-analytics rollup". |
| List Candidates | Paginated candidate retrieval with filters by source, stage, recently active, posting. Useful for "this morning, who advanced to onsite yesterday" digest workflows for hiring managers. |
| List Jobs | Returns open requisitions with team, location, status. Useful for "auto-post our open roles to the company careers page" sync workflows and for routing inbound applications to the right job. |
Pre-built Ashby workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Ashby once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Ashby field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Ashby integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Ashby to Tiny Command?
What Ashby triggers does Tiny Command support?
What Ashby actions can I run from a workflow?
Is the Ashby integration real-time?
Do I need to write code to use Ashby with Tiny Command?
How much does the Ashby integration cost?
More hr & recruiting apps people connect.
Same category as Ashby, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Ashby.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
