Connect Ai ml api to Ashby

When something happens in Ai ml api, Notis takes the next step in Ashby. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Ai ml api to Ashby

View example

Turn an AI-screened profile into an Ashby candidate

Send a vetted candidate profile from an AI agent into Ashby so recruiters can continue from a complete candidate record.

View example

Add AI research context to an Ashby candidate

Turn notes or analysis from an AI agent into a candidate note in Ashby, keeping relevant context on the profile.

View example

Tag Ashby candidates from AI skill analysis

Use submitted AI analysis to apply an existing Ashby tag to a candidate, making relevant profiles easier to find.

View example

Route AI-sourced candidates to an Ashby project

Associate an identified candidate with an Ashby sourcing project when an AI agent submits a relevant profile.

View example

Create an Ashby application from a vetted profile

When an AI workflow has identified a candidate and a relevant job, create an application in Ashby with the supplied source details.

View example

Correct Ashby application source from AI review

Use a reviewed source finding from an AI workflow to update the attribution on an identified Ashby application.

View example

Prepare recurring candidate follow-up notes

On a schedule, have an AI workflow review supplied recruiting context and add a concise follow-up note to a selected Ashby candidate.

View example

Refresh candidate tags from scheduled AI review

On a recurring schedule, use supplied candidate analysis to apply an existing Ashby tag that helps keep profiles organized.

View example

File reviewed candidates into Ashby sourcing projects

Run a scheduled organization pass that adds identified, reviewed candidates to their specified existing Ashby sourcing projects.

Supported Triggers and Actions

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

Ai ml api 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 recruiting project.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Candidate Tag

Add an existing tag to a candidate’s profile.

ActionInstant

Add Hiring Team Member

Assign a team member to a hiring team.

ActionInstant

Add User to Interviewer Pool

Add a user to a pool of interviewers.

ActionInstant

Add Opening Job

Link an existing job to a job requisition.

ActionInstant

Add Opening Location

Associate a location with an existing job requisition.

ActionInstant

Anonymize Candidate

Irreversibly anonymizes a candidate’s personal data; all applications must be archived or hired.

ActionInstant

Approve Offer

Approve an offer or a specific step in its approval process.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.