Keep approved hiring fields aligned across Airtable and Ashby
When the Airtable hiring base changes shape, ask Notis to check the approved field specification and create its Ashby counterpart.
Trigger
Base Schema Changed
Triggers when tables, fields, or views change in an Airtable base.
Action
Create Custom Field
Create a new custom field in Ashby. Custom fields allow you to track additional structured data on Ashby objects like candidates, applications, and jobs. This action creates the field definition that can then be populated with values using the set custom field value actions. Supported field types: - String: Free text input - Number: Numeric values - Boolean: True/false values - Date: Date values (optionally date-only without time) - ValueSelect: Single selection from predefined options - MultiValueSelect: Multiple selections from predefined options - Employee: Reference to an Ashby employee (limited object type support) Note: ValueSelect and MultiValueSelect field types require the selectableValues parameter. Requires the hiringProcessMetadataWrite permission.
Why this helps
A new hiring field can be added to Airtable while recruiters still lack a place to record that information in Ashby.
- Reduce missed field setup after an approved Airtable change.
- Use explicit field details instead of guessing from an alert.
- Keep the matching Airtable field name available for reference.
Setup
Build it in a few focused steps.
- 1Connect Airtable and Ashby once in Notis.
- 2Create an automation and provide the approved Airtable-to-Ashby field specifications, including supported type and values.
- 3In one instruction, ask Notis to create only the Ashby custom fields covered by those specifications when the Airtable schema changes.
- 4Choose the Airtable Base Schema Changed trigger and select where run reports should go.
- 5Test with one approved field change and verify the custom field details in Ashby.
Questions about this workflow
Does a schema change event provide the new field definition?
The event indicates that the base schema changed, but field names, types, and values must be available to Notis or supplied in your approved specification.
Will it create every new Airtable field in Ashby?
Only ask it to create fields that belong in Ashby and whose supported type and values are specified. The event alone does not establish that mapping.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airtable to Ashby. A trigger fires from one place; an action lands in another.
Airtable 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.
Base Metadata Changed
Triggers when an existing Airtable base changes its name or permission level.
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.
Base Schema Changed
Triggers when tables, fields, or views change in an Airtable base.
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.
User Profile Changed
Triggers when the connected Airtable user's profile information changes.
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.
View Created
Triggers when a new view is created in an Airtable base.
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.
View Deleted
Triggers when a previously known Airtable view is deleted.
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.
View Metadata Changed
Triggers when an Airtable view changes its name or type.
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.
Airtable 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.