Connect ActiveMerge to Ashby

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

View example

Turn an ActiveMerge candidate document into an Ashby profile

Use candidate details from an ActiveMerge document to create an Ashby candidate profile and reduce manual entry.

View example

Attach ActiveMerge document context to an Ashby candidate

Add useful context from a submitted ActiveMerge document to the relevant Ashby candidate as a note.

View example

Tag Ashby candidates from ActiveMerge review details

Apply an existing Ashby candidate tag based on review details submitted from an ActiveMerge document workflow.

View example

Add document-sourced candidates to an Ashby project

Organize an identified candidate in an existing Ashby sourcing project using details submitted from ActiveMerge.

View example

Put interview prep document takeaways on an Ashby candidate

Summarize submitted interview preparation material into a concise Ashby candidate note for the hiring team.

View example

Create an Ashby job from an approved ActiveMerge role brief

Turn a submitted, approved role brief into a draft job record in Ashby for hiring team review.

View example

Create an Ashby opening from a headcount brief

Create an Ashby opening from headcount details submitted with an ActiveMerge requisition document.

View example

Submit an employee referral from an ActiveMerge intake

Use submitted referral intake details to create a formal Ashby referral for a specified job.

View example

Add a weekly recruiting document follow-up note

On a schedule, review supplied outstanding document follow-ups and add a concise note to the relevant Ashby candidate.

Supported Triggers and Actions

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

ActiveMerge 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.