Ashby Integration & Approval Workflow Automation
Run Ashby on autopilot. Keep the veto.
125 actions
That candidate update you meant to review ships before you catch the mistake. Rills proposes the action, you approve from your phone.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential project management action from Ashby arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Create 5 referrals from pending applicants?
3 applicants from last week's job fair
2 referral requests in draft status
Same pattern as last Monday's batch
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Ashby automation
Recruitment notifications pile up faster than you can read them. Ashby sends referral submissions, department moves, location changes, and custom field updates. The ones AI gets wrong are the ones that show up in support tickets at 2am.
When Ashby runs unsupervised
Let Ashby automation run unchecked and actions ship without review. A move department call shifts a candidate queue before you see the error. A referral creates an entry with wrong contact info. A custom field value overwrites a hiring manager's notes.
- List Jobs: pulls outdated postings into a published feed, confusing applicants
- Move Department: shifts a candidate who was supposed to stay in current pipeline
- Set Custom Field Values: replaces manually entered ratings with default values
- Create Referral: sends an invitation to the wrong email address
- Update Location Name: changes office city on all open positions simultaneously
What Rills does inside Ashby
Rills intercepts operations like Move Department, Set Custom Field Values, and Create Referral, proposing them to you first. You see the candidate name, the new department, or the fields about to change. Then you decide.
The update still happens; you just see it before it goes out.
Why Ashby has no triggers and how Rills fills the gap
Ashby's API does not push events when data changes. For project management purposes, Rills polls on a schedule or waits for an upstream trigger from another tool. Common patterns include:
- Scheduled syncs: Rills checks Ashby for new survey submissions every hour and proposes action
- Upstream workflow: An incoming email from a candidate triggers Rills to List Jobs and then Create Referral
- Batch operations: Every Monday morning, Rills reviews pending Location Name updates and proposes them for approval
What Rills can do in Ashby
6 of 125 actions across reads, writes, and updates.
- 01
Change Application Stage
Move candidates through different stages of your hiring pipeline, from initial application review through offers and hiring decisions. This keeps your recruitment process organized and ensures candidates progress smoothly based on your interview plan.
- 02
List Applications
Retrieve all job applications submitted to your hiring process, with support for filtering and pagination to manage large volumes of applicants. This helps you keep track of every candidate in your recruitment pipeline.
- 03
Update Application
Modify key properties of a job application in Ashby, including source attribution, credited recruiter, and creation date. This helps maintain accurate candidate tracking and ensures proper credit assignment in your hiring pipeline.
- 04
Create Candidate
Add a new candidate to your recruitment system with their contact details and social profiles, ready to apply to open positions.
- 05
List Candidates
Retrieve a list of all candidates in your hiring pipeline with optional filtering and pagination to stay updated on your recruitment progress.
- 06
Search Candidates
Quickly locate specific candidates in your hiring pipeline by searching for their email address or name, enabling you to retrieve candidate information without browsing through full lists.
Common questions about Ashby automation
How do I automate moving a department in Ashby without losing control?
Set a rule: when a candidate is hired, Rills proposes moving their department. You review the change on your phone and swipe to approve before it updates in Ashby. Nothing ships without your okay.
Can I get mobile approval before creating a referral in Ashby?
Yes. Rills proposes a referral when conditions match, like a new contact. You see the candidate details on your phone and decide to approve or ignore. No referral fires without your approval.
How do I set custom field values in Ashby automatically?
Define a workflow: when an applicant reaches a stage, Rills proposes updating a custom field. You approve the action from your phone. Only after your approval does the field update. You stay in control.
Can I automate listing job postings with human approval first?
Absolutely. Rills proposes publishing a job posting based on your rules. You review the draft on your phone and approve before it goes live. No job goes out that you haven't seen first.
How do I automate updating location names in Ashby?
Set a rule: when a location changes externally, Rills proposes the update. You see the change on your phone and approve. Only then does Ashby update. No accidental location mistakes.
How is Rills different from Zapier for Ashby automation?
Zapier fires automatically once set. If a trigger misfires, changes ship without you. Rills proposes each action to you first. You approve from your phone before anything changes. You keep the veto.
Does Rills support Ashby webhooks?
Ashby webhooks aren't needed. Rills monitors your data and proposes actions based on your rules. You approve each proposed action from your phone before it runs. No event setup required.
How much does Rills cost for Ashby automation?
Approvals and workflow logic are free. You only pay for real actions executed, like API calls to Ashby. No monthly subscription for the approval queue or mobile app. Pay only for what ships after you approve.