Skip to content
Notis

Handle OneRoster OAuth requests through Notis

Make approved OneRoster authentication checks available through a controlled workflow.

Trigger

Webhook received

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

Action

OneRoster OAuth2 Base API

Tool to interact with Blackbaud OneRoster OAuth2 base endpoints. Use to fetch OpenID configuration (/.well-known/openid-configuration), JWKS key set (publickeys), or obtain an access token via the client credentials grant. Ensure client credentials are configured before using the token operation.

Why this helps

Authentication setup checks become a context switch when every request requires manual endpoint work.

  • Standardize authentication checks
  • Return configuration details to the requesting system
  • Reduce manual endpoint handling

Setup

Build it in a few focused steps.

  • 1Connect Blackbaud in Notis once and configure the required client credentials.
  • 2Create an automation named OneRoster OAuth Check.
  • 3Tell Notis which allowed operation to perform: OpenID configuration, JWKS retrieval, or client credentials token request.
  • 4Choose a Notis webhook trigger and select a secure report channel.
  • 5Send one authorized test request.

Questions about this workflow

What operations are supported?

OpenID configuration, JWKS key retrieval, and client credentials token acquisition.

Can this work without configured credentials?

No. Configure the required Blackbaud client credentials before testing token operations.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Zendesk 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 one or more gifts (donations) to an existing gift batch in Blackbaud Raiser's Edge NXT. Use this tool when you need to: - Append new gifts to an open batch for later processing - Batch multiple donations together before committing them - Add gifts with detailed information (payments, splits, custom fields) Prerequisites: - The batch must already exist (use a create batch action first if needed) - The batch must be in "open" status (not committed) - You need the batch_id (system record ID) and constituent_id (donor ID) for each gift Note: This action returns response details for all HTTP status codes (including errors). Check the status_code field in the response to determine success (200) vs errors (4xx/5xx).

ActionInstant

Webhook trigger

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

TriggerInstant

Get Gift By ID

Retrieves comprehensive gift details from Blackbaud Raiser's Edge NXT by gift ID. Use this tool when you need to fetch detailed information about a specific gift including: - Gift amount and currency - Donor/constituent information - Gift type and status - Important dates (gift date, post date) - Associated metadata and custom fields The gift_id is the unique system record ID (integer) that identifies the gift in Raiser's Edge NXT.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Get Membership Details

Retrieves comprehensive membership details from Blackbaud Raiser's Edge NXT by member junction ID. Fetches detailed information about a specific membership including program name, category/subcategory, membership status and standing (Active, Lapsed), start/expiration dates, dues information, and associated constituent ID. Requires a valid member_junction_id (GUID) that uniquely identifies a membership junction record linking a constituent to a membership program in Raiser's Edge NXT. Returns error information in the response object for graceful error handling in agent workflows.

ActionInstant

New Zendesk Ticket

Triggers when a new ticket is created in a specified Zendesk view.

TriggerPolling

Get Payment Transaction

Retrieves payment transaction details from Blackbaud SKY Payments API. Use this to check transaction status, amounts, payment methods, and error details. Transaction IDs come from payment processing endpoints, checkout callbacks, batch operations, or webhook notifications. Requires: Payments API subscription key (Bb-Api-Subscription-Key) and OAuth Bearer token. This retrieves existing transactions; it does not process new payments.

ActionInstant

OneRoster OAuth2 Base API

Tool to interact with Blackbaud OneRoster OAuth2 base endpoints. Use to fetch OpenID configuration (/.well-known/openid-configuration), JWKS key set (publickeys), or obtain an access token via the client credentials grant. Ensure client credentials are configured before using the token operation.

ActionInstant

Connect any two apps with Notis in the middle.

Zendesk and Blackbaud, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Blackbaud.