Connect Adyntel to Async interview

When something happens in Adyntel, Notis takes the next step in Async interview. 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 Adyntel to Async interview

View example

Review candidate responses alongside ad insights

On a schedule, review interview responses and use Adyntel insights to prepare a concise hiring follow-up brief.

View example

Triage interview responses on demand

Start a response review with a webhook and have Notis summarize candidate responses, using Adyntel insights when relevant.

View example

Refresh interview job details with campaign context

On a schedule, review interview jobs and relevant Adyntel insights, then update a job when you specify what should change.

View example

Update an interview job when priorities change

Trigger a targeted review of an existing interview job and use Adyntel insights as context for the update you requested.

View example

Review open interview jobs with campaign context

Get a scheduled list of existing interview jobs with a concise review informed by Adyntel insights where useful.

View example

Pull an interview job inventory when needed

Request an on-demand list of existing interview jobs and a concise summary with relevant Adyntel campaign context.

View example

Spot recurring themes in interview responses

Review candidate responses on a schedule, summarize recurring themes, and add relevant Adyntel insights as separate context.

View example

Prepare a candidate follow-up brief on demand

Use a webhook to review candidate responses and prepare a focused follow-up brief with relevant Adyntel context.

Supported Triggers and Actions

Notis builds workflows that link Adyntel to Async interview. A trigger fires from one place; an action lands in another.

Adyntel triggers

Async interview actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Delete Job

Permanently delete an interview job; this cannot be undone.

ActionInstant

Webhook trigger

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

TriggerInstant

List Jobs

Retrieve a list of interview jobs.

ActionInstant

List Interview Responses

Retrieves interview responses with candidate details.

ActionInstant

Update Job

Update an existing interview job.

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.