Keep OneRoster authentication checks routine
Schedule a OneRoster base API request and send the run report to the channel your team checks.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Integration maintenance checks can be forgotten when authentication setup is handled only during a launch or incident.
- Give routine integration checks a dependable cadence.
- Keep request outcomes visible in run reports.
- Reduce the need for manual reminders.
Setup
Build it in a few focused steps.
- 1Connect Blackbaud once in the Notis portal and configure the required client credentials if requesting a token.
- 2Create an automation in Automations, New Automation, or tell Notis what outcome you want from any channel.
- 3Ask Notis to fetch the OneRoster configuration or request a token as appropriate for your check.
- 4Choose a recurring schedule and report destination.
- 5Test the selected request and confirm the report contains the expected result.
Questions about this workflow
Can I use this to request a token?
Yes, when client credentials are configured. The action supports the OAuth2 client credentials grant.
Can this action fetch donor data?
No. It interacts with OneRoster OAuth2 base endpoints.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Blackbaud. A trigger fires from one place; an action lands in another.
Stripe triggers
Blackbaud actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
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.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
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.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
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.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe 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.