Connect Addresszen to Docuseal

When something happens in Addresszen, 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 Addresszen to Docuseal

View example

Send a Docuseal template after an Addresszen validation

When your system sends a validated Addresszen address payload, create a Docuseal signature request from the supplied template and signer details.

View example

Email a Docuseal request to a validated recipient

Use an Addresszen webhook containing a validated recipient address and email to create a Docuseal submission from a known template.

View example

Create a Docuseal request from a validated-address DOCX

When your Addresszen service sends a validated address and a DOCX document, create a one-off Docuseal signing request with supplied variables.

View example

Create a Docuseal HTML request from Addresszen output

Use a supplied Addresszen validation webhook and HTML form content to start a Docuseal signing request.

View example

Review a Docuseal submission tied to an Addresszen payload

On a schedule, retrieve a specific Docuseal submission using the submission ID stored in a supplied Addresszen webhook or export.

View example

Download documents for an Addresszen-linked submission

On a schedule, retrieve documents for the exact Docuseal submission ID supplied by your Addresszen export or webhook.

View example

Update a Docuseal submitter from Addresszen data

Use a supplied Addresszen webhook payload to update an exact Docuseal submitter, resend a request, or prefill values when explicitly instructed.

View example

Archive a completed Docuseal request after delivery confirmation

When a supplied Addresszen webhook confirms the related delivery details, archive the exact Docuseal submission ID you provide.

Supported Triggers and Actions

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

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