Connect Abuselpdb to Dock certs

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

View example

Create a replacement API key after an IP risk alert

When a webhook reports suspicious access, check the IP with Abuselpdb and create a restricted Dock certs API key if the alert calls for rotation.

View example

Verify a credential after screening its source IP

When a credential arrives with an IP address, check the IP reputation and ask Dock certs to verify the credential or presentation.

View example

Review credential inventory on a schedule

On a recurring schedule, retrieve Dock certs credential metadata and check supplied IP threat indicators with Abuselpdb for a concise review report.

View example

Review Dock certs API keys on a schedule

List Dock certs API keys on a recurring schedule and include Abuselpdb checks for IP indicators your team supplies or the run receives.

View example

Retrieve a credential when an IP review is requested

For an incoming review request, check its IP with Abuselpdb and retrieve the specified Dock certs credential, using a supplied password only when appropriate.

View example

Resolve a DID referenced in a threat report

Check an IP from an incoming threat report with Abuselpdb, then retrieve the supplied DID document so a reviewer can inspect identity details.

View example

Review revocation registries on a schedule

Retrieve Dock certs revocation registries periodically and include any supplied IP threat context in a report for credential reviewers.

View example

Review Dock certs webhooks on a schedule

List configured Dock certs webhooks on a recurring schedule and check any IP indicators supplied for the review against Abuselpdb.

View example

Create a Dock certs webhook for a monitored threat workflow

When a monitoring request arrives, check its IP with Abuselpdb and create a Dock certs webhook endpoint if the request meets your stated criteria.

Supported Triggers and Actions

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

Abuselpdb triggers

Dock certs actions

Recurring trigger

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

TriggerScheduled

Create API Key

Creates a new API key.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Webhook

Creates a webhook endpoint.

ActionInstant

Delete API Key

Deletes an API key.

ActionInstant

Delete Credential

Deletes a verifiable credential.

ActionInstant

Delete Tag

Permanently deletes a tag.

ActionInstant

Delete Webhook

Deletes a webhook.

ActionInstant

Retrieve API Key

Retrieves details about an API key.

ActionInstant

Retrieve API Keys

Lists all API keys for the account.

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.