Start Ashby applications from Jira approvals
Once a Jira update records a clear hiring approval, Notis can start the related Ashby application for the candidate and role.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Create Application
Create a new job application by associating a candidate with a job opening in Ashby ATS. Use this action to: - Add a candidate to a job's hiring pipeline and interview process - Track the source of the application (referral, job board, etc.) - Credit a user (recruiter/referrer) for bringing in the candidate - Place the candidate directly into a specific interview stage (optional) The created application will automatically be assigned to the job's hiring team and start tracking the candidate's progress through the interview stages. Required: candidateId and jobId must reference existing entities in Ashby.
Why this helps
Hiring approvals can be recorded in Jira while the next pipeline step waits for someone to create the application in Ashby.
- Turn an explicit approval into the next recruiting action.
- Reduce delay between a decision and pipeline setup.
- Keep the application tied to the approved Jira context.
Setup
Build it in a few focused steps.
- 1Connect Jira and Ashby once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe the approval update that qualifies, how to identify the candidate and job, and what application source details to include.
- 4Pick the Jira Updated Issue trigger for the configured project and choose where run reports go.
- 5Test with one real approved update and verify the application in Ashby.
Questions about this workflow
Will this create an application if approval is unclear?
The instruction should require explicit approval and identifiable candidate and job records. Ask Notis to report incomplete or ambiguous requests.
Can the application be created for a candidate not yet in Ashby?
This action associates a candidate with a job. If no candidate record exists, create or resolve the candidate first.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Ashby. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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 Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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.
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.
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.
Jira 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.