Create an Ashby application from a recruiting post
Move candidate submissions from internal posts into the hiring pipeline.
Trigger
New Blog Post Created
Triggers when a new blog post is created in Confluence. Optionally filters by space or status.
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
Candidate referrals and submissions wait in internal documentation.
- Shorten referral processing time
- Reduce duplicate entry
- Keep submissions traceable
Setup
Build it in a few focused steps.
- 1Connect Confluence and Ashby.
- 2Create an automation that creates an application from complete candidate submissions.
- 3Pick New Blog Post Created as the trigger.
- 4Choose where reports and exceptions should go.
- 5Test with one structured recruiting post.
Questions about this workflow
Can it process informal posts?
Ask Notis to create an application only when the required candidate and job details are present.
What if the candidate already exists?
Instruct Notis to identify the existing candidate before creating the application.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Confluence to Ashby. A trigger fires from one place; an action lands in another.
Confluence 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 Attachment Added
Triggers when a new attachment is uploaded to a Confluence page. Optionally filters by media type.
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.
Blog Post Added to Label
Triggers when a new blog post is added to a specific label in Confluence.
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.
Blogpost Inline Comment Added
Triggers when a new inline comment is added to a Confluence blog post.
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.
Blog Post Like Count Changed
Triggers when a Confluence blog post's like count changes (someone likes or unlikes).
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.
Blog Post Updated
Triggers when a Confluence blog post is updated (any edit that creates a new version).
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.
Content Restrictions Changed
Triggers when view or edit restrictions change on a Confluence page or blog post. Detects user/group restrictions being added, removed, or modified.
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.
Confluence 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.