Skip to content
Notis

Capture recruiting introductions in Ashby

Keep promising introductions from getting lost in a busy inbox. Notis can turn a new Agent mail message into an Ashby candidate profile for your team to review.

Trigger

New Email Received

Trigger for new emails in an AgentMail inbox

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

Manually copying names, email addresses, and referral context from recruiting emails creates friction and leaves candidates easy to overlook.

  • Reduce manual candidate data entry.
  • Preserve the introduction context for recruiter review.
  • Keep new prospects visible in Ashby.

Setup

Build it in a few focused steps.

  • 1Connect Agent mail and Ashby once in Notis.
  • 2Create an automation in Notis and name it.
  • 3In one instruction, ask Notis to create an Ashby candidate from recruiting introductions and include relevant context from the email.
  • 4Pick the Agent mail New Email Received trigger and choose where run reports go.
  • 5Test with one real introduction email.

Questions about this workflow

Will every incoming email become a candidate?

Describe which messages count as recruiting introductions in your instruction. Notis can analyze the email, but it cannot rely on a filter you have not described.

Does this create an application too?

No. This workflow creates a candidate profile. Use a separate application action when you want to place someone into a job pipeline.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Agent mail 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

New Email Received

Trigger for new emails in an AgentMail inbox

TriggerPolling

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

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

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

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

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

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.

Agent mail 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.