Catch Recurring Donation Problems Instantly
Flag a recurring donation concern and instantly see payment transaction status - no missed renewals, no surprised donors.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
Recurring donation failures go unnoticed because monitoring happens in separate systems, causing lost revenue and donor churn.
- Catch payment failures immediately
- Prevent recurring revenue loss
- Protect donor relationships
- Reduce churn from payment issues
Setup
Build it in a few focused steps.
- 1Connect Linear and Blackbaud to Notis.
- 2Ask Notis: 'When a recurring donation issue status changes to flagged, check the transaction status in Blackbaud - is the latest payment successful or failed?'
- 3Select 'Issue Updated' as your trigger.
- 4Use Slack alerts so you catch failures in real-time, not in reports.
- 5Test with a real recurring donation issue - payment status appears instantly.
Questions about this workflow
How often does Notis check payment status?
Notis checks whenever you flag an issue. For continuous monitoring, ask Notis to 'check all recurring donations daily' using a scheduled automation.
What if a payment failed?
Notis reports the failure reason (declined, expired card, insufficient funds) so you can contact the donor with a specific fix.
Can this prevent future failures?
Yes - if you set up a recurring schedule, Notis can alert you before the next payment attempt so you can update card info proactively.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Blackbaud. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
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.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.