Connect Adtraction to Documenso

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

View example

Turn an approved Adtraction partner into a Documenso agreement

Start a Documenso agreement from an Adtraction partner approval, using a selected template and the partner details provided with the request.

View example

Prepare a signing envelope for changed partner commission terms

Create a Documenso envelope when a webhook reports updated Adtraction commission terms, so the revised terms can be documented for signing.

View example

Create a Documenso document for an Adtraction partner contract

Use a webhook request carrying a partner contract PDF to create a Documenso document, then upload the file to the returned presigned URL.

View example

Prepare a refreshed partner agreement template each month

On a monthly schedule, review the Adtraction partner agreement material you provide and create a refreshed Documenso template with a supplied PDF.

View example

Review available templates for upcoming partner onboarding

On a weekly schedule, review the partner onboarding needs you specify and list available Documenso templates to help choose the right starting point.

View example

Add partner signers to a Documenso envelope in bulk

Create the recipient list for an existing Documenso envelope from a webhook request with partner signer details and roles.

View example

Build a weekly inventory of partner agreement documents

Run a weekly Documenso document search to review agreement records alongside the Adtraction partner follow-up information you provide.

View example

Add a partner as a signer to an existing Documenso document

Add one partner signer to a specified existing Documenso document using details supplied in an Adtraction-related webhook request.

View example

Add signing fields to a partner agreement template in bulk

Use a webhook request to add multiple configured signature or input fields to an existing Documenso partner template.

Supported Triggers and Actions

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

Adtraction triggers

Documenso actions

Recurring trigger

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

TriggerScheduled

Create Embedding Presign Token V2 Beta

Creates a token for embedded document and template editing sessions.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Document Beta

Creates a document and returns a temporary upload link for its PDF.

ActionInstant

Delete Document Fields

Deletes one or more fields from a document.

ActionInstant

Create Document Field

Adds one field to a document in draft status.

ActionInstant

Delete Template

Permanently deletes a template; this action cannot be undone.

ActionInstant

Create Document Fields (Bulk)

Adds multiple fields to a draft document; each must reference a valid recipient.

ActionInstant

Distribute Document V2

Sends a draft document to recipients for signing for the first time.

ActionInstant

Create Document Recipient

Adds a recipient, such as a signer, viewer, or approver, to a document.

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.