Skip to content
Notis

Capture Talent from Your Issues Automatically

Stop copy-pasting candidate info from issue threads into Ashby. When you mention someone who might be great for a role, Notis creates their candidate profile instantly.

Trigger

Public Team Issue Created

Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.

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

Great candidates are mentioned in issues--in feedback, referral threads, and comments--but capturing them requires context-switching to Ashby and manual data entry, leading to lost opportunities.

  • Captures every referred candidate without context-switching
  • Builds candidate pool from internal team feedback
  • Creates profiles with zero manual entry

Setup

Build it in a few focused steps.

  • 1Connect your Linear and Ashby accounts to Notis once via the portal integrations page.
  • 2In the Notis portal, go to Automations - New Automation and name it (e.g., 'Issue Talent to Candidate').
  • 3Write your automation prompt: 'When a new issue is created in my public team, extract any candidate names and details mentioned, then create a candidate profile for each in Ashby.'
  • 4Select the trigger 'Issue Created' for your public teams and choose a Slack or email channel to report runs.
  • 5Test by creating an issue that mentions a candidate's name and experience, then verify the profile appears in Ashby.

Questions about this workflow

Will this create duplicate candidates?

Notis uses candidate name and email to detect duplicates, so re-running the automation or mentioning the same candidate again won't create a second profile.

What information does it capture?

It extracts name, email (if provided), company, role, and skills from the issue or comments. You can also guide the prompt to look for specific details your team typically includes.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Linear to Ashby. A trigger fires from one place; an action lands in another.

Linear 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

Comment Received Trigger

Triggered when a comment is received.

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

Issue Created Trigger

Triggered when a new issue is created.

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

Issue Updated Trigger

Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

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

Private Team Comment Created

Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).

TriggerPolling

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

Private Team Issue Created

Fires when a new issue appears in a private Linear team (polled with the connected user's token).

TriggerPolling

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

Private Team Issue Properties Updated

Fires when properties on an issue change in a private Linear team (polled with the connected user's token).

TriggerPolling

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.

Linear 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.