Connect ActiveMerge to Dropcontact

When something happens in ActiveMerge, Notis takes the next step in Dropcontact. 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 Dropcontact

View example

Enrich an inbound prospect list

Send a contact list to a Notis webhook and enrich up to 250 records with verified email and company details.

View example

Start enrichment for a contact intake

Start asynchronous Dropcontact enrichment when a webhook receives an eligible contact intake, then retain its request ID for result retrieval.

View example

Retrieve completed enrichment results

On a schedule, retrieve Dropcontact results for request IDs supplied to the automation and summarize completed contact data.

View example

Fetch results after an enrichment notification

Use an incoming webhook to start a results retrieval run when an external process reports that enrichment is complete and supplies its request ID.

View example

Review configured enrichment webhooks

Run a scheduled inventory of Dropcontact webhook subscriptions and summarize the configured subscriptions for review.

View example

Audit webhook URLs and event types

Schedule a detailed inventory of Dropcontact webhook URLs, event types, and subscription details for account review.

View example

Subscribe to enrichment result notifications

Create a Dropcontact webhook subscription for enrichment result notifications when an HTTP request supplies the callback URL.

View example

Update a webhook subscription from a request

Use a webhook request to update an existing Dropcontact subscription's callback URL, rate limiting settings, or active status.

View example

Remove an obsolete webhook subscription

When a webhook request identifies a subscription for removal, delete it in Dropcontact and report the result.

Supported Triggers and Actions

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

ActiveMerge triggers

Dropcontact actions

Recurring trigger

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

TriggerScheduled

Create Webhook Subscription

Creates a subscription for automatic enrichment completion notifications.

ActionInstant

Webhook trigger

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

TriggerInstant

List Webhook Subscriptions

View configured webhook subscriptions.

ActionInstant

Delete Webhook Subscription

Deletes a webhook subscription and stops notifications; it can instead be paused.

ActionInstant

Retrieve Enrichment Results

Retrieve contact enrichment results for a submitted request.

ActionInstant

Initiate Contact Enrichment

ActionInstant

List Webhook Subscriptions V2

Lists the account’s configured webhook subscriptions.

ActionInstant

Update Webhook Subscription

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.