Connect Adtraction to Blackbaud

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

View example

Prepare Approved Adtraction Commissions for Gift Batch Review

Turn approved Adtraction commissions into draft gifts in an existing Blackbaud Raiser's Edge NXT batch for finance review.

View example

Collect Ready Adtraction Commissions into a Blackbaud Batch

On a schedule, use supplied Adtraction commission data to add eligible items to an existing Blackbaud gift batch.

View example

Look Up a Blackbaud Gift from an Adtraction Reference

Use a supplied Adtraction-linked reference to retrieve details for a specific Blackbaud gift and return a concise review summary.

View example

Review Blackbaud Gift Status for Commission Follow-Up

On a recurring schedule, retrieve specified Blackbaud gifts linked to commission records and summarize status and dates for follow-up.

View example

Check Blackbaud Payment Status for an Adtraction-Related Case

Retrieve Blackbaud SKY Payments transaction details from a supplied transaction ID and summarize the outcome with its Adtraction case reference.

View example

Review Blackbaud Payment Exceptions on a Schedule

Run a scheduled review of supplied Blackbaud transaction IDs and summarize statuses or errors with their Adtraction case references.

View example

Check Blackbaud Membership Details from a Partner Case

Retrieve a Blackbaud membership by member junction ID and summarize its standing and dates alongside a supplied Adtraction-related case reference.

View example

Review Membership Standing for Open Partner Cases

On a schedule, retrieve supplied Blackbaud memberships and summarize standing, expiration dates, and dues details alongside case references.

View example

Check Blackbaud OneRoster API Access from a Partner Request

Use the Blackbaud OneRoster base API action to retrieve its OpenID configuration, public keys, or a client credentials token when configured.

Supported Triggers and Actions

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

Adtraction triggers

Blackbaud actions

Recurring trigger

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

TriggerScheduled

Add Gifts To Batch

Add gifts to an existing open batch for later processing.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Gift By ID

Retrieve the details of a gift by its identifier.

ActionInstant

Get Membership Details

Retrieve the details and status of a membership.

ActionInstant

Get Payment Transaction

Retrieve the status and details of an existing payment transaction.

ActionInstant

OneRoster OAuth2 Base API

Fetch OAuth configuration or public keys, or obtain an access token.

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.