Move candidates in Ashby when ClickUp status changes
Record the decision once in ClickUp and keep the candidate pipeline current.
Trigger
Task Status Updated
Triggers when a task's status changes. `changes[]` carries `StatusChange` entries only — ClickUp pre-filters server-side by event type. Lower traffic than subscribing to `CLICKUP_TASK_UPDATED` and pattern-matching `StatusChange`.
Action
Change Application Stage
Move an application to a different interview stage in the hiring pipeline. Use this to: - Advance candidates to the next interview stage (e.g., from "Application Review" to "First Round") - Move candidates to any stage within their job's interview plan (forward or backward) - Archive applications by moving to an Archived stage (requires archiveReasonId) - Move to Offer or Hired stages when progressing candidates Important: The interview stage must belong to the same interview plan as the application's job. Use LIST_INTERVIEW_STAGES with the application's job interview plan ID to get valid stage options.
Why this helps
Recruiters lose time updating the same hiring decision in multiple systems.
- Keep pipeline stages current
- Reduce missed handoffs
- Make recruiting decisions visible to the team
Setup
Build it in a few focused steps.
- 1Connect ClickUp and Ashby in the Notis portal.
- 2Create an automation that interprets defined ClickUp statuses and moves the matching Ashby application to the appropriate stage.
- 3Pick ClickUp Task Status Updated as the trigger.
- 4Select a report channel, then test with one task tied to a real application.
Questions about this workflow
How does Notis know which application to update?
Tell Notis how your ClickUp tasks identify candidates and applications, such as an application ID or stable candidate reference.
Can it handle backward moves?
Yes. Ask Notis to move the application forward or backward according to the status instructions you provide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clickup to Ashby. A trigger fires from one place; an action lands in another.
Clickup triggers
Ashby actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Candidate to Project
Add a candidate to a project in Ashby. Projects are sourcing initiatives or recruiting campaigns used to organize and track candidate pipelines. Use this to associate candidates with specific sourcing efforts. Common use cases: - Adding sourced candidates to recruiting campaigns - Organizing candidates by sourcing channel or initiative - Tracking candidates in specific hiring projects Requires candidatesWrite permission. Returns the updated candidate object on success, or error details if the candidate or project is not found.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Candidate Tag
Add a tag to a candidate in Ashby. Use this to categorize and organize candidates with existing tags from the system. This action allows you to apply labels/tags to candidates for filtering, searching, and organizational purposes. Tags must already exist in the system - use LIST_CANDIDATE_TAGS to view available tags or CREATE_CANDIDATE_TAG to create new ones. The response includes the full updated candidate object when successful, showing the newly added tag in the candidate's tags array. If a candidate already has the tag, the operation will still succeed idempotently.
Folder Created
Triggers when a new Folder is created.
Add Hiring Team Member
Add an Ashby user to a hiring team at the application, job, or opening level. Use this when you need to assign a team member to participate in the hiring process with a specific role. Requires the organizationWrite permission.
Folder Deleted
Triggers when a Folder is deleted.
Add User to Interviewer Pool
Add a user to an interviewer pool. Use this to assign interviewers to interview pools for scheduling and coordination. Requires the hiringProcessMetadataWrite permission.
Folder Updated
Triggers when a Folder is updated (renamed, content edited, etc.).
Add Opening Job
Adds a job to an opening (job requisition) in Ashby ATS. An opening represents a position to be filled, while a job defines the role details. This action associates an existing job with an existing opening, allowing multiple jobs to be linked to a single opening. Use this when you need to add job definitions to an opening or when creating multi-role requisitions. Requires the jobsWrite permission. On success, returns the updated opening with the job added to its jobIds array. On failure, returns error details with specific error codes.
List Created
Triggers when a new List is created.
Add Opening Location
Tool to add a location to an opening (job requisition). Use when you need to associate a location with an existing opening. Requires the jobsWrite permission.
List Deleted
Triggers when a List is deleted.
Anonymize Candidate
Anonymize a candidate by removing personally identifiable information. Use this when you need to permanently anonymize a candidate's data. This action cannot be reversed and requires all of the candidate's applications to be in the archived or hired state.
List Updated
Triggers when a List is updated (renamed, content edited, etc.).
Approve Offer
Approve an offer or a specific approval step within an offer's approval process. This action supports two modes: - Complete offer approval: Provide only offerId to approve the entire offer - Step-specific approval: Provide offerId, approvalStepId, and userId to approve a specific step When approving a specific step, both approvalStepId and userId are required together. Requires the 'offersWrite' permission.
Connect any two apps with Notis in the middle.
Clickup and Ashby, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Ashby.