Connect Agile CRM to Ashby

When something happens in Agile CRM, 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 Agile CRM to Ashby

View example

Turn a Recruiting Prospect into an Ashby Candidate

Send a qualified recruiting prospect from Agile CRM to Ashby as a candidate, preserving the supplied contact and profile details.

View example

Add Referral Context to an Ashby Candidate

On a recurring schedule, review supplied Agile CRM referral context and add a concise note to the matching Ashby candidate.

View example

Start an Ashby Application for a Qualified Contact

When a chosen Agile CRM contact is ready for a specific role, use a webhook handoff to create an Ashby application with supplied job and candidate details.

View example

Label Ashby Candidates from CRM Segments

Periodically use supplied Agile CRM segment context to add an existing Ashby tag to matching candidates.

View example

Place a Sourced Contact in an Ashby Project

Send a selected Agile CRM sourcing contact to the appropriate Ashby project using a webhook request with the candidate and project context.

View example

Refresh Ashby Application Source from CRM Context

Review available Agile CRM attribution context on a schedule and update the source on a matching Ashby application when the correct source is clear.

View example

Move an Ashby Application After a Recruiting Decision

Use an explicit webhook handoff to move a matching Ashby application to the supplied interview stage after a recruiting decision is made.

View example

Keep an Ashby Candidate Brief Current

On a recurring schedule, summarize relevant available Agile CRM interaction context into a concise Ashby candidate note.

View example

Create an Ashby Candidate from a Referral Handoff

Accept a selected referral handoff from Agile CRM through a webhook and create an Ashby candidate with the supplied contact details.

Supported Triggers and Actions

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

Agile CRM 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.