BP Function: Get Pledge History After
Fetches a user's pledge history after a specified date. If you are only interested in a small recent time range you may want to use this to avoid processing unneeded pledge history entries later (e.g. when searching for a previously-pledged tier). It is recommended to still request a little more than you need (e.g. if you are only interested in pledges in June you may want to request pledges starting in May to capture cases where a user started their pledge on May 30 and was entitled to that tier during June).
Inputs
-
Token InfoAPI Token InfoThe user's API access token. Usually obtained via oauth.
-
Start DateDate TimePledge events with timestamps earlier than this date will not be included in the results
-
Discard UnpaidBoolIf true, pledge events with invalid payment states (e.g. declined payments) will not be included in the results
-
Campaign IDStringIf not empty, will only process pledge events with a matching campaign ID and discard others
Outputs
-
Main Execution Pin (at the top)
Execution will immediately continue from this pin while the request is processing in the background. Do not use execution flowing from this pin to check for the results, they aren't ready yet!
-
Async ActionThis is a reference to the action running in the background. You can use this to cancel the async action if you decide you actually don't need the results before it has completed.
-
On Complete
When the user's data has been successfully fetched, execution will flow from this pin.
Pledge Historyshould be valid and can be used at this point. -
On Fail
If the process fails for any reason, execution will flow from this pin. You can use this to display an error to the user, prompt them to try again, etc.
Pledge Historywill be invalid and should not be used! -
Pledge HistoryPatreon Pledge HistoryThe user's pledge history
For any questions, help, suggestions or feature requests, please feel free to contact me at nbpsup@gmail.com