SecureGive Integration¶
Our integration with SecureGive provides periodic imports of SecureGive transactions and, optionally, updates of member records. Both modules–transactions imports and member updates–utilize Python scripts. Therefore, they can be configured to run nightly by adding them to your Morning Batch script, or as often as every 15 minutes by adding them to your Scheduled Tasks script.
Transaction Import¶
When the transaction import script is run, TouchPoint checks with SecureGive for recent transactions (by default, from the last seven days). New transactions (those not previously imported) are imported into batches corresponding to their SecureGive batch.
Important
If a transaction is imported into a closed TouchPoint batch, the batch is reopened and left in that state. This should be rare since, typically, transactions for the same batch are imported together.
Donors are assigned to the imported transactions by the following process:
A search is made for a record with an extra value named SecureGiveId that matches the member ID on the transaction.
When no match is found in step 1, the SecureGive member record is retrieved and a search is made for a record that matches the SecureGive name and either email address or phone number.
If there is no unique match in step 2 (i.e., either no match or more than one match), a new record is created with the information in the SecureGive member record.
When a donor is assigned in either step 2 or 3, a SecureGiveId extra value is added to the record with the SecureGive member ID.
Member updates¶
When the member update script is run, TouchPoint checks with SecureGive for recent updates to member records and the TouchPoint record with the matching SecureGiveId extra value is updated with the information on the SecureGive record.
When a TouchPoint record is checked against a SecureGive member record, an extra value named SecureGiveUpdate is placed on the TouchPoint record with the value of the SecureGive member record’s last change date.
During the update, SecureGive member records are processed only if their last change date is later than the TouchPoint record’s SecureGiveUpdate value. In other words, the record is checked for changes only if the SecureGive update happened after the last import update to the TouchPoint record.
Setting Up the SecureGive Integration¶
If your church is interested in this integration, contact Support. You will be asked for an API key from your SecureGive account.
Latest Update |
08/13/2024 |
Added this article