Connect Agent mail to Docugenerate

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

View example

Turn new lead emails into a sales brief

Create a consistent lead brief from each new inquiry email using your Docugenerate template.

View example

Create a support case summary from an email

Turn new support emails into a structured case summary with your Docugenerate template.

View example

Prepare a meeting brief from an email thread starter

Create a meeting prep document when a new email contains a proposed meeting or discussion topic.

View example

Build a vendor intake record from a new email

Generate a vendor intake document from details explicitly included in a new email.

View example

Create a decision log entry from a decision email

Capture an explicit decision in an email as a structured Docugenerate log entry.

View example

Generate a batch of documents from a webhook

Use a webhook payload containing multiple records to generate a ZIP of documents from a Docugenerate template.

View example

Schedule a review of your document templates

Run a scheduled Docugenerate template listing so your team can review available templates and metadata.

View example

Generate a PDF with supplied attachments

Start a Docugenerate document run from a webhook request and include files supplied with the request.

View example

Generate and merge a PDF packet

Use a webhook to generate a Docugenerate PDF and append supplied PDF files into one document.

Supported Triggers and Actions

Notis builds workflows that link Agent mail to Docugenerate. A trigger fires from one place; an action lands in another.

Agent mail triggers

Docugenerate actions

Recurring trigger

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

TriggerScheduled

Generate documents from template

Tool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.

ActionInstant

Webhook trigger

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

TriggerInstant

Generate documents as ZIP

Tool to bulk generate multiple documents into a ZIP archive. Use when you need a batch of docs packaged as ZIP.

ActionInstant

New Email Received

Trigger for new emails in an AgentMail inbox

TriggerPolling

Generate document with attachments

Tool to generate a PDF with embedded attachments. Use when you need to bundle extra files into the PDF output.

ActionInstant

Generate document with merge

Tool to generate a PDF and append additional PDF files. Use when you need to merge extra pages into a generated document.

ActionInstant

Update Document

Tool to update a document's metadata. Use when renaming an existing document after confirming the document ID.

ActionInstant

Get or list templates

Tool to retrieve or list existing templates. Use when needing template IDs and metadata before making updates or generating documents.

ActionInstant

Update Template

Tool to update a template’s file and settings. Use after confirming the template ID and desired inputs.

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.