Keep useful sourcing context with the candidate
Send a candidate ID and your observation to Notis. It adds the context as a note on the Ashby profile.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Candidate Note
Create a note on a candidate profile. Use this to add comments, observations, or feedback about a candidate during the recruitment process.
Why this helps
Good context from a screening call or sourcing conversation is easy to lose in scattered messages and personal notes.
- Keep observations alongside the candidate record.
- Reduce the time spent copying notes into the ATS.
- Make follow-up easier with context in one place.
Setup
Build it in a few focused steps.
- 1Connect Ably and Ashby once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to add each supplied observation as a note to the specified Ashby candidate.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real candidate ID and a suitable note.
Questions about this workflow
What does the request need to identify?
Provide the Ashby candidate identifier and the note content you want added.
Will Notis generate observations about the candidate?
This workflow records the context you supply. It does not claim to assess a candidate or retrieve missing information.
Does this change the candidate's pipeline stage?
No. It adds a note to the candidate profile and does not change an application stage.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to Ashby. A trigger fires from one place; an action lands in another.
Ably 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.
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.
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.
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.
Ably 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.