Skip to content
Notis

Keep Ashby candidate labels aligned with Asana sections

Move a hiring task into the section that signals a useful recruiting category, and Notis can apply the corresponding existing Ashby tag.

Trigger

Task Moved to Section

Triggers when a task is moved to a section in a project.

Action

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.

Why this helps

Teams often track candidate categories in project sections but forget to maintain the same labels in the ATS.

  • Keep candidate labels consistent with task organization.
  • Reduce manual tagging after a recruiting handoff.
  • Make candidates easier to filter in Ashby.

Setup

Build it in a few focused steps.

  • 1Connect Asana and Ashby once in the Notis portal.
  • 2Create an automation explaining which task section corresponds to which existing Ashby candidate tag and how to identify the candidate.
  • 3Pick Asana's Task Moved to Section trigger for the recruiting project.
  • 4Choose where Notis should send run reports.
  • 5Test with one real task move and confirm the existing tag on the intended Ashby candidate.

Questions about this workflow

Can this create a new Ashby tag?

No. The Add Candidate Tag action requires a tag that already exists in Ashby. Create the tag in Ashby before using this workflow.

Does moving a task itself identify the candidate?

Not necessarily. Give Notis a clear identifier in the task, such as the candidate's name or email, and specify the section-to-tag meaning 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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Attachment Added to Task

Triggers when an attachment is added to a task.

TriggerInstant

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.

ActionInstant

New Comment on Task

Triggers when a comment is added to a task in a project.

TriggerInstant

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.

ActionInstant

New Task Created

Triggers when a new task is created in a project.

TriggerInstant

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.

ActionInstant

Task Moved to Section

Triggers when a task is moved to a section in a project.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

Task Updated

Triggers when a task is updated in a project.

TriggerInstant

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.

ActionInstant

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.