Connect Abuselpdb to Agent mail

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

View example

Email an IP reputation check

When a webhook supplies an IP address, check its reputation with Abuselpdb and email the result to your chosen recipient.

View example

Email a scheduled abuse report digest

On a schedule, retrieve abuse reports from Abuselpdb and email a concise digest to your chosen recipient.

View example

Email confirmation after an IP report

When a webhook supplies an IP to report, ask Abuselpdb to report it and email a summary of the result.

View example

Email a weekly threat intelligence review

On a recurring schedule, retrieve threat intelligence from Abuselpdb and email a review based on the scope you provide.

View example

Find inbox messages about a flagged IP

When a webhook sends an IP address, check its reputation with Abuselpdb, then list Agent mail messages relevant to that IP for review.

View example

Review inbox messages alongside threat checks

On a schedule, check the Abuselpdb threat intelligence scope you specify and list relevant Agent mail messages for follow-up.

View example

Inspect a specific email for IP context

When a webhook provides a message identifier and IP address, retrieve that Agent mail message and check the IP with Abuselpdb for review.

View example

Collect inbox context for an abuse report

When a webhook provides an IP, check it with Abuselpdb and list Agent mail messages that may contain context for an abuse report.

Supported Triggers and Actions

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

Abuselpdb triggers

Agent mail actions

Recurring trigger

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

TriggerScheduled

Get Message

Retrieves the full details of an email message from an inbox.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Draft

ActionInstant

List Messages

Lists messages in an inbox.

ActionInstant

Create Inbox

ActionInstant

Send Email

Sends an email.

ActionInstant

Create Inbox API Key

ActionInstant

Delete Thread

ActionInstant

Get API Key

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.