Connect Abuselpdb to Conveyor

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

View example

Create a Vendor Review from an IP Threat Signal

Turn a webhook carrying an IP threat signal into a Conveyor vendor review for security follow-up.

View example

Submit a Security Questionnaire with Threat Context

On a recurring schedule, prepare a Conveyor questionnaire submission using current IP threat context and the submission details you provide.

View example

Open a Questionnaire Request from a Threat Signal

Use an incoming security signal and supplied submitter details to create a Conveyor questionnaire request for processing.

View example

Review Open Questionnaires Alongside Threat Intelligence

On a schedule, list Conveyor questionnaires and use current Abuselpdb findings to flag items that may need security attention.

View example

Answer a Product Security Question with Threat Context

Use a webhook request to submit one product line question to Conveyor and include relevant Abuselpdb context in the answer workflow.

View example

Scan Conveyor Interactions for IP Threat Follow-up

Review Conveyor's available interactions on a schedule and flag those that may need attention based on current IP threat intelligence.

View example

Add Threat Context to a Questionnaire Request

When a new signal arrives, update an existing Conveyor questionnaire request with the supplied external reference or source details.

View example

Audit Trust Center Authorizations with Threat Context

On a schedule, review Conveyor authorizations and flag records that may warrant access review based on supplied threat context.

View example

Update a Trust Document with a Verified Threat Notice

Use a webhook containing an approved notice and document reference to update Conveyor document metadata with relevant security context.

Supported Triggers and Actions

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

Abuselpdb triggers

Conveyor actions

Recurring trigger

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

TriggerScheduled

Delete a Conveyor document

Deletes a document.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete folder

Permanently deletes a folder; this cannot be undone.

ActionInstant

Get all access groups

Retrieves all access groups for a program.

ActionInstant

Get Authorization Request

Retrieves details about an authorization request.

ActionInstant

Get authorizations

Retrieves Trust Center authorizations; a valid API token is required.

ActionInstant

Get Authorization Requests

Retrieves authorization requests.

ActionInstant

Get all Conveyor connections

Retrieves all connections.

ActionInstant

Get all Conveyor documents

Retrieves all documents from the trust center.

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.