Skip to content
Notis

Create Ashby openings from Google Tasks

Convert approved headcount decisions into trackable requisitions.

Trigger

Task List Changed

Triggers when a task list changes (title or content updates). This trigger monitors a specific Google Tasks list and fires when changes are detected.

Action

Create Opening

Create a new opening (job requisition) in Ashby ATS. An opening represents a job requisition - a request to hire for a specific position. All parameters are optional, but typically you'll want to provide at least a title, job IDs, and location IDs for a meaningful opening. Use this action to: - Create a new job opening with specific requirements - Associate openings with existing jobs, locations, and teams - Set hiring targets, employment type, and opening state - Track backfill positions vs new roles Required permission: openingsWrite Note: To get valid IDs for teamId, locationIds, and jobIds, use the corresponding List Departments, List Locations, and List Jobs actions.

Why this helps

Approved hiring plans sit idle because opening creation is separated from planning work.

  • Reduce requisition lag
  • Keep headcount plans traceable
  • Give recruiters a clear starting point

Setup

Build it in a few focused steps.

  • 1Connect Google Tasks and Ashby in Notis once.
  • 2Create an automation for approved opening requests.
  • 3Tell Notis to create an Ashby opening from the changed list only when approval and role details are present.
  • 4Pick Task List Changed as the trigger.
  • 5Choose a report channel and test with one approved planning update.

Questions about this workflow

Can it wait for approval language?

Yes. Instruct Notis to act only when the list explicitly indicates approval.

What if job IDs are missing?

Have Notis report the request for completion before creating the opening.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Google Tasks 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 Task Created

Triggers when a new task is created in a Google Tasks list. Uses timestamp filtering (updatedMin) to efficiently detect new tasks.

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

New Task List Created

Triggers when a new Google Tasks task list is created. This trigger monitors Google Tasks and fires when new task lists are detected.

TriggerPolling

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

Task Details Changed

Triggers when a specific task's details change. This trigger monitors a single Google Task and fires when any of its details (title, notes, status, due date, completion, position) are modified.

TriggerPolling

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

Task List Changed

Triggers when a task list changes (title or content updates). This trigger monitors a specific Google Tasks list and fires when changes are detected.

TriggerPolling

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

Task Updated

Triggers when an existing task is updated in a Google Tasks list. This trigger monitors a specific task list and fires when tasks are modified.

TriggerPolling

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.

Google Tasks 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.