This article covers the Salesforce-side configuration required to connect your Salesforce account with GiveNow. There are three steps: install the GiveNow managed package, create a connected application, and configure duplicate and OAuth settings.
Before starting, make sure you have initiated the setup from OrgHQ. See How do I set up the Salesforce integration in OrgHQ?
Step 1: Install the GiveNow managed package
The setup email sent from OrgHQ contains two links: one for the Production package and one for the Sandbox package. Select the appropriate link, log in to your Salesforce account, and follow the package installation instructions.
The installation may take a few minutes. Once complete, the GiveNow Integration Upgrade package will appear in your list of installed packages.
Step 2: Create a connected application
- Log in to your Salesforce account.
- Go to Setup.
- Go to Apps > App Manager.
- Select New Connected App.
- Enter a Connected App Name. We recommend starting with "GiveNow" followed by your organisation name.
- The API Name will be generated automatically.
- Enter a Contact Email for the person responsible for maintaining the connected app.
- Under API (Enable OAuth Settings), select Enable OAuth Settings.
- In the Callback URL field, enter:
https://www.givenow.com.au/smarty-file/integrations/18/authorized - Under Selected OAuth Scopes, add "Manage user data via APIs (api)" and "Perform requests at any time (refresh_token, offline_access)".
- Select Save. You will be redirected to your connected app page.
- Record the Consumer Key and Consumer Secret. You will need these to complete the OrgHQ configuration.
Step 3: Disable duplicate alerts
To prevent duplicate alerts from blocking the integration, disable alerts for both accounts and contacts:
- Go to Setup > Data > Duplicate Management > Duplicate Rules.
- Select Standard Account Duplicate Rule, then select Edit.
- Set Action On Create to "Allow" with Alert unchecked and Report checked.
- Set Action On Edit to "Allow" with Alert unchecked and Report checked.
- Select Save.
- Repeat for Standard Contact Duplicate Rule.
Step 4: Verify OAuth policies
- Go to Setup > Apps > Connected Apps > Manage Connected Apps.
- Select your GiveNow connected app.
- Under OAuth Policies, verify that the Permitted Users field is set to "All users may self-authorize." If not, select Edit Policies and update it.
- Select Save.
Wait 5–10 minutes for Salesforce to enable the application, then return to OrgHQ and enter the Consumer Key and Consumer Secret to complete the connection. See How do I set up the Salesforce integration in OrgHQ?
GiveNow managed package components
The GiveNow Integration Upgrade package adds custom fields, record types, and page layouts to your Salesforce instance. These are used to store and display GiveNow-specific data.
Contact fields
- GiveNow Contact Reference: References the GiveNow contact identifier.
Campaign fields and record types
- GiveNow Giving: Record type for cause campaigns.
- GiveNow Regular Giving: Record type and page layout for regular donation campaigns.
- Date of the Last Donation / Date of the Next Donation: Tracks regular donation timing.
- Frequency (GiveNow): Donation frequency (One-Off, Daily, Weekly, Monthly, Quarterly, Annually).
- GiveNow Giving Payment Method: Credit Card or Direct Debit.
- GiveNow Cause ID: The unique cause URL reference.
- GiveNow Cause Status: The cause status (Incomplete, Pending, Approved, Rejected, Deleted, Closed, Hidden Open).
- Regular Donor: Reference to the Salesforce contact.
- GiveNow Regular Giving Status: Active, Inactive, Failed, Cancelled, or Expired.
Opportunity fields
- GiveNow Record Type: Optional record type for GiveNow donations.
- GiveNow Integration Notes: Details about how the campaign and contact were resolved.
- GiveNow Receipt Number: Corresponds to the donation receipt number.
- Frequency (GiveNow): Donation frequency.
Other considerations
- GiveNow-specific fields are not visible in the standard page layout. You may need to add them to your page layouts or create new ones.
- Consider setting up field-level security for users accessing GiveNow-specific fields.
- Consider setting up a Process Builder automation to update the standard Campaign Status field based on the custom GiveNow Cause Status field.