Connect DonorPerfect to Gravity Forms

Both apps 69DonorPerfect 38Gravity Forms 31

• Trigger
  New donor

  Polling trigger. Fires when a new donor is added in DonorPerfect. Polls the dp table ordered by donor_id descending; dedups on each record's donor_id.

• Trigger
  New gift

  Polling trigger. Fires when a new gift (donation) is created in DonorPerfect. Polls the dpgift table ordered by gift_id descending; dedups on each record's gift_id.

• Trigger
  New or updated donor

  Triggered when a donor is added or updated.

• Trigger
  New or updated gift

  Triggered when a gift (donation) is created or modified.

• Trigger
  Two-way sync new or updated donors

  A trigger for two-way syncing new and updated donors, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.

• Trigger
  Two-way sync new or updated gifts

  A trigger for two-way syncing new and updated gifts (donations), with enhanced on-the-fly mapping. Polls the DonorPerfect dpgift table.

• Action
  Add code

  Adds a new code and description to the DPCODES table. Allows you to add things like new GL Code, Solicitation, Campaign code and other code values administered in the Code Maintenance screen of DPO.

• Action
  Add contact

  Adds a contact (activity/task) record to a donor in DonorPerfect via the dp_savecontact stored procedure. Supply Donor Id, Activity Code, and contact details.

• Action
  Add donor

  Creates a new donor in DonorPerfect via the dp_savedonor stored procedure. Leave Donor Id empty (0) to create; the new donor_id is returned. Common fields: first/last name, address, city, state, zip, email, phones.

• Action
  Add gift

  Creates a new gift (donation) for a donor in DonorPerfect via the dp_savegift stored procedure. Supply Donor Id, Amount, Gift Date and code fields (GL, Solicit, Sub-solicit, Gift Type, Campaign).

• Action
  Add new donor gift

  Creates a new donation (gift) for the donor with the specified ID.

• Action
  Add new donor gift by email

  Creates a new donation for the donor with the specified email. The gift will only be added if the donor's email is found.

• Action
  Add new pledge

  Adds a new pledge to the specified donor. If successful, the pledge's ID is output.

• Action
  Add other info

  Adds an Other Info (user-defined) record to a donor in DonorPerfect via the dp_saveotherinfo stored procedure. Supply Donor Id, the field name and value.

• Action
  Add other info by email

  Adds "other info" for the first donor found with the given email address. The other info is not added if the email address is not found.

• Action
  Delete donor

  Deletes the donor with the specified Donor Id from DonorPerfect via the dp_deletedonor stored procedure.

• Action
  Find filters by name

  Returns one or more filters that match the specified name. Supports wildcard matching. An empty result is returned if no matching filter is found.

• Action
  Get 20 donor field values

  Returns up to 20 field values for the specified donor. An error occurs if the donor is not found.

• Action
  Get active code by description

  Returns the code having the specified description. An error occurs if the code is not found or is inactive.

• Action
  Get active code description

  Gets the specified code's description. An error occurs if the code is not found or is inactive.

• Action
  Get code description

  Returns the description for a code value in the specified DPO code field (e.g. GL, CAMPAIGN, SOLICIT) from the dpcodes table.

• Action
  Get donor

  Returns all available fields for the donor with the specified Donor ID from the DPO donor (dp) table.

• Action
  Get donor by email

  Returns the DonorPerfect donor whose email address matches the one supplied, including the donor's user-defined field values. An error occurs if no donor has that email address.

• Action
  Get donor by email, first name, and last name

  Returns all available donor fields if one or more donor matches the email, first name, and last name. No error occurs if a donor is not found, the emitted 'donor_id' will be empty instead.

• Action
  Get donor default field info

  Returns information about the specified donor field.

• Action
  Get donor default fields

  Returns all default fields for donors.

• Action
  Get donor gifts

  Returns all gifts (donations) for the donor with the specified Donor ID from the DPO dpgift table.

• Action
  Get donors by filter

  Returns the donor IDs that match the saved DPO filter with the specified Filter ID, via the dp_filterids stored procedure.

• Action
  Get donor user-defined field info

  Returns information about the specified donor user-defined field.

• Action
  Get donor user-defined fields

  Returns all user-defined donor fields.

• Action
  Get donor user-defined field values

  Returns all user-defined field values for the specified donor. An error occurs if the donor is not found.

• Action
  Get field display type

  Gets the specified field's display type, which can either be "code" or "description"

• Action
  Get flags by donor ID

  Returns the specified donor's flags. No error occurs if the donor is not found.

• Action
  Get gift

  Returns all fields for the gift (donation) with the specified Gift ID from the DPO dpgift table.

• Action
  Get gift user-defined field values

  Returns all user-defined field values for the specified gift (donation). An error occurs if the gift is not found.

• Action
  List filters

  Returns the ID and name of all saved DPO filters that have non-empty names from the dpfilter table.

• Action
  Post pledge payment

  Posts a payment to the specified pledge for the specified donor.

• Action
  Update donor

  Updates an existing donor in DonorPerfect via the dp_savedonor stored procedure. Supply the Donor Id of the record to update along with the field values.

• Trigger
  Form Submission

  Triggers when the specified form is submitted.

• Action
  Add Entry Note

  Adds a note to a form entry. Use it to write a progress record back onto a submission — for example noting that the submission was synced to your CRM, who handled it, or why it was skipped — so the note is visible to anyone reviewing that entry in WordPress.

• Action
  Create Entry

  Creates a new form entry.

• Action
  Create Feed

  Attaches a new add-on feed to a form. A feed is one add-on's configuration on a form — the rule that says what should happen when the form is submitted, such as creating a WordPress user, adding the person to a mailing list, or taking a payment.

• Action
  Create Form

  Creates a new form on the WordPress site and returns its id. Supply the form's title and, if you want the form ready to collect data, the fields it should show.

• Action
  Create Form Feed

  Attaches a new add-on feed to a named form. Does the same thing as Create Feed, but takes the form as part of the address rather than in the settings — use whichever reads better in your automation.

• Action
  Delete Entry

  Removes a form entry. By default the entry is moved to the trash and can still be restored from the Entries list; you can choose instead to delete it outright so it cannot be recovered.

• Action
  Delete Feed

  Permanently removes an add-on feed from a form, so that add-on no longer acts on the form's submissions. The form itself and its entries are untouched.

• Action
  Delete Form

  Moves a form to the trash on the WordPress site. The form stops accepting submissions and disappears from the forms list, and the site owner can still restore it or empty the trash in WordPress.

• Action
  Delete Note

  Permanently removes an entry note. Use it to clear a note you logged against a submission, for example after a failed sync was retried successfully.

• Action
  Get Entry

  Retrieve a single form entry, including every field value the person submitted.

• Action
  Get Feed

  Returns one add-on feed by its id, including the add-on's settings. A feed is one add-on's configuration attached to a form — the rule that says what should happen when the form is submitted.

• Action
  Get Form

  Returns one form's full definition, including every field on it, its notifications and its confirmations. Use it to read a form's field ids and labels before mapping data into that form.

• Action
  Get Form Results

  Returns the summarised answers for a survey, quiz or poll form — how many people picked each choice, and how many answered each free-text question — rather than the individual entries. On a form with a lot of entries the summary is built in the background, so the result can come back marked as still being calculated.

• Action
  Get Note

  Returns a single entry note by its id, including the note text, the entry it belongs to, when it was recorded and who it is credited to.

• Action
  List Entries

  Returns form entries from across every form on the site, newest first, and can narrow the results to one form or to entries whose answer to a chosen question matches a value you give.

• Action
  List Entry Notes

  Returns every note attached to one form entry — both notes people have added and the notes Gravity Forms records automatically, such as notification failures. Use it to read back what has already been logged against a submission.

• Action
  List Feeds

  Returns every add-on feed configured on the site. A feed is one add-on's configuration attached to a form — the rule that says what should happen to a submission, such as sending it to a mailing list or charging a payment.

• Action
  List Form Entries

  Returns the entries submitted on one particular form, newest first, and can narrow them to entries whose answer to a chosen question matches a value you give.

• Action
  List Form Feeds

  Returns the add-on feeds attached to one form — the rules that say what happens when that form is submitted. Returns an empty list when the form has no feeds.

• Action
  List Forms

  Returns every active form on the WordPress site, with each form's id, title and entry count. Use it to look up the id a form needs before working with that form's entries.

• Action
  List Notes

  Returns every entry note on the site, across all forms and entries. Use it to sweep recently logged notes when you do not already know which entry you are looking for; to read the notes on one known entry, use List Entry Notes instead.

• Action
  Send Entry Notifications

  Sends the notification emails an entry's form is set up to send, for an entry that already exists — useful for re-sending a confirmation, or for notifying people about an entry that was created through the API rather than by someone filling the form in.

• Action
  Submit Form

  Submit a form the way a visitor would — Gravity Forms runs the form's own validation, saves the entry, and fires its notifications and confirmation.

• Action
  Update Entry

  Change the answers on an existing form entry. Answers you leave blank keep the values they already have.

• Action
  Update Entry Properties

  Changes an entry's housekeeping flags without touching any of its answers — whether it is starred, whether it counts as read, and whether it sits in the active list, the trash or spam.

• Action
  Update Feed

  Changes an existing add-on feed's settings. Settings you do not include are left as they are, so you can change one thing without restating the rest of the add-on's configuration.

• Action
  Update Feed Properties

  Switches an add-on feed on or off, and sets the order it runs in. The add-on's own settings are left completely untouched, so this is the safe way to pause a feed without risking its configuration.

• Action
  Update Form

  Replaces an existing form's definition with the one you supply. Gravity Forms overwrites the whole form, so read the form first with Get Form and send back every part of it you want to keep.

• Action
  Update Note

  Replaces the text of an existing entry note. Use it to revise a note you logged earlier against a submission — for example updating "Sync started" to "Synced to CRM as contact 4821".

• Action
  Validate Submission

  Checks a set of answers against a form's own validation rules without saving an entry or sending any notifications. Returns whether the answers would be accepted, and the per-field error messages when they would not.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.