Capture prospective hires from Asana in Ashby
Put a candidate lead in an Asana task and let Notis create the Ashby profile, so recruiting details start in the hiring system without extra copying.
Trigger
New Task Created
Triggers when a new task is created in a project.
Action
Create Candidate
Create a new candidate in the system. Use this to add candidates with their contact information and social profiles before applying them to jobs.
Why this helps
Promising leads can stay buried in project tasks while recruiters retype their details into the ATS.
- Reduce duplicate data entry during candidate intake.
- Keep new candidate records in Ashby as leads are captured.
- Get a run report for visibility into the result.
Setup
Build it in a few focused steps.
- 1Connect Asana and Ashby once in the Notis portal.
- 2Create an automation by telling Notis to create an Ashby candidate from a new Asana task intended to capture a prospective hire.
- 3Pick Asana's New Task Created trigger for the relevant project.
- 4Choose where Notis should send run reports.
- 5Test with one real hiring task and review the Ashby candidate.
Questions about this workflow
Does this create an application too?
No. It creates a candidate profile. Creating an application requires a separate Ashby action and a job or opening to associate.
What should the Asana task include?
Include the candidate details available to you, such as a name and contact information. Notis can only use information present in the task or otherwise supplied in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Ashby. A trigger fires from one place; an action lands in another.
Asana 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.
Attachment Added to Task
Triggers when an attachment is added to a task.
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.
New Comment on Task
Triggers when a comment is added to a task in a project.
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.
New Task Created
Triggers when a new task is created in a project.
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.
Task Moved to Section
Triggers when a task is moved to a section in a project.
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.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
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.
Task Updated
Triggers when a task is updated in a project.
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.
Asana 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.