Connect ActiveMerge to Docuseal

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

View example

Send ActiveMerge PDFs for signature

Start a Docuseal signature request when ActiveMerge sends a completed PDF and signer details.

View example

Create Docuseal requests from generated DOCX files

Use an ActiveMerge generated DOCX with dynamic tags to start a Docuseal signature request.

View example

Start signing from ActiveMerge HTML

Send generated HTML to Docuseal as a one-off signable submission when ActiveMerge completes a document.

View example

Save generated HTML as a Docuseal template

Create a reusable Docuseal template from HTML supplied by an ActiveMerge workflow.

View example

Turn an ActiveMerge PDF into a reusable template

Create a Docuseal template from an ActiveMerge PDF for repeat signing workflows.

View example

Send ActiveMerge prepared agreements from a Docuseal template

Use a prepared Docuseal template to send an ActiveMerge workflow's agreement to named signers.

View example

Review Docuseal templates for upcoming ActiveMerge work

On a schedule, list Docuseal templates and identify which ones match upcoming document work supplied to Notis.

View example

Get a scheduled Docuseal signing status digest

Review Docuseal submissions on a schedule and summarize their status for ActiveMerge document follow-up.

View example

Audit the Docuseal template library for document operations

Run a scheduled, filtered inventory of Docuseal templates and report useful findings for ActiveMerge workflows.

Supported Triggers and Actions

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

ActiveMerge triggers

Docuseal actions

Recurring trigger

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

TriggerScheduled

Archive Template

Archives a template.

ActionInstant

Webhook trigger

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

TriggerInstant

Archive Submission

Archives a submission, which can be restored and is not permanently deleted.

ActionInstant

Create Submission From PDF

Creates and sends a one-off PDF submission for electronic signature.

ActionInstant

Clone Template (v2)

Clones an existing template into a new template.

ActionInstant

Create Template from HTML

Creates a fillable document template from HTML.

ActionInstant

Create Submission

Creates and sends signature requests from an existing template.

ActionInstant

Get Template

Retrieves a template’s details.

ActionInstant

Create Submissions From Emails

Creates a submission for a template and sends each recipient a unique signing link.

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.