Check payment transaction status on a schedule
Get a recurring view of the Blackbaud payment transactions you need to monitor, with returned errors ready for follow-up.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
Payment checks can become scattered manual tasks, making it harder to notice a failed or unresolved transaction promptly.
- Gather selected transaction statuses in a recurring run report.
- Make payment errors easier to spot and follow up.
- Reduce the need to open each transaction manually.
Setup
Build it in a few focused steps.
- 1Connect Blackbaud in the Notis portal once.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis which transaction IDs to retrieve and how to summarize statuses, amounts, methods, and errors in the run report.
- 4Choose a recurring schedule as the trigger and select where run reports should go.
- 5Test with one real transaction ID and confirm the returned details are useful.
Questions about this workflow
Where do transaction IDs come from?
They must come from a payment processing endpoint, checkout callback, batch operation, webhook notification, or another source you provide. The lookup action requires transaction IDs.
Does this retry or change a payment?
No. The action retrieves transaction details, including status and error information. It does not process or retry payments.
Can the schedule find every transaction by itself?
The listed action retrieves details by transaction ID. Provide the IDs or a supported way to supply them in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Blackbaud. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Connect any two apps with Notis in the middle.
Jira 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.