Author 诗语

The WP Fusion CRM API

#Overview
WP Fusion takes a completely original approach to connecting WordPress to our supported CRMs and marketing automation systems. There is no other plugin available that is as flexible or extensible.
Normally, with a plugin like Gravity Forms (for example), you would download one of several available add-ons that connect Gravity Forms to your CRM of choice, like the ActiveCampaign add-on or AgileCRM add-on. These are created from scratch and use code unique to the API in question.
Before WP Fusion, many sites would have to use several different plugins to get a basic level of integration with their CRM. An ActiveCampaign user might need ActiveCampaign add-on for Gravity Forms, ActiveWoo to send WooCommerce order data, and the official ActiveCampaign plugin to enable site tracking and embedding forms.
This introduces a lot of unnecessary overlap, with the ActiveCampaign SDK being included multiple times, and redundant API calls being sent.
#How we solved that problem
When designing WP Fusion, we realized that all of these CRM systems offer the same basic functionality: adding new contacts, updating existing contacts, applying and removing tags, and loading contact data from the CRM.
So with that in mind, we created a wrapper class for each CRM, with a standardized set of functions to send and receive data from WordPress, then reformat it according to the rules of each API. Every one of our integrations has at least the following methods:
#connect()
wp_fusion()->crm->connect( $auth = null, $test = false );
The connect() function is called by all the member functions in the class to initialize the connection to the CRM. It』s not necessary to use this in your code, but it can be used to validate an API key or OAuth token by setting $test to true.
Parameters:

$auth (string) (Optional) The API key or other authorization code required to connect. There may be more than one parameter depending on the CRM. If this is left blank, WP Fusion will use the authentication data you entered on the original setup page.
$test (bool) (Optional) If set to true, WP Fusion will also verify the connection by attempting to make an API call.

Return values:

true (bool) If the connection was successful
$error (WP_Error object) If the connection was unsuccessful

#sync_tags()
wp_fusion()->crm->sync_tags();
Loads all available tags from the CRM and updates the available tags in the tag dropdowns for WP Fusion.
Return values:

$tags (array) An array of tags in the CRM
$error (WP_Error object) If the API call failed

#sync_crm_fields()
wp_fusion()->crm->sync_crm_fields();
Loads all available fields and custom fields from the CRM and updates the available fields in the dropdowns for WP Fusion.
Return values:

$crm_fields (array) An array of available fields in the CRM
$error (WP_Error object) If the API call failed

#get_contact_id()
wp_fusion()->crm->get_contact_id( $email_address );
Looks up a contact ID in the CRM by their email address.
Parameters:

$email_address (string) The email address to search for a contact by

Return values:

$contact_id (int) A contact ID for that email address
false (bool) If no contact ID was found with that email address
$error (WP_Error object) If the API call failed

#get_tags()
wp_fusion()->crm->get_tags( $contact_id );
Loads a contact』s tags from the CRM.
Parameters:

$contact_id (int) The contact ID to load tags for

Return values:

$tags (array) An array of tag IDs for the contact (or an empty array if no tags were found)
$error (WP_Error object) If the API call failed

#apply_tags()
wp_fusion()->crm->apply_tags( $tags, $contact_id );
Applies one or more tags to a contact.
Parameters:

$tags (array) An array of tags to apply
$contact_id (int) The contact ID to apply the tags to

Return values:

true (bool) The tags were successfully removed
$error (WP_Error object) If the API call failed

#remove_tags()
wp_fusion()->crm->remove_tags( $tags, $contact_id );
Removes one or more tags to a contact.
Parameters:

$tags (array) An array of tags to remove
$contact_id (int) The contact ID to remove the tags from

Return values:

true (bool) The tags were successfully removed
$error (WP_Error object) If the API call failed

#add_contact()
wp_fusion()->crm->add_contact( $contact_data, $map_meta_fields = true );
Adds a new contact to the CRM.
Parameters:

$contact_data (array) An associative array containing the data for the new contact, with the WordPress field as the key and the data as the value, like array( 'user_email' => '[email protected]' );
$map_meta_fields (bool) If set to true, WP Fusion will convert the field keys from WordPress meta keys into the field names in the CRM. Set to false to bypass this conversion.

Return values:

$contact_id (int) The contact ID for the newly created contact
$error (WP_Error object) If the API call failed or the data was rejected

#update_contact()
wp_fusion()->crm->update_contact( $contact_id, $contact_data, $map_meta_fields = true );
Updates a contact in the CRM.
Parameters:

$contact_id (int) The contact ID to update
$contact_data (array) An associative array containing the update data, in the same format as add_contact();
$map_meta_fields (bool) If set to true, WP Fusion will convert the field keys from WordPress meta keys into the field names in the CRM. Set to false to bypass this conversion.

Return values:

true (bool) The contact was successfully updated
$error (WP_Error object) If the API call failed or the data was rejected

#load_contact()
wp_fusion()->crm->load_contact( $contact_id );
Loads the contact record for a contact ID and returns an associative array of WordPress field / value pairs, based on the WP Fusion 「Contact Field」 settings.
Parameters:

$contact_id (int) The contact to load

Return values:

$user_meta (array) Array containing the contact data
$error (WP_Error object) If the API call failed or the contact was not found

#load_contacts()
wp_fusion()->crm->load_contacts( $tag_id );
Searches the CRM for any contacts with the specified tag and returns an array of contact IDs.
Parameters:

$tag (int or string) The tag to search by

Return values:

$contact_ids (array) Array of contact IDs returned by the search. Will be an empty array if no results were found
$error (WP_Error object) If the API call failed

See the next section for more information on how to utilize WP Fusion』s core helper functions while interfacing with your CRM.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

Detecting and Syncing Additional Fields

#Overview
If you』re reading this page then you』re probably trying to sync a field value with your CRM that isn』t currently supported by WP Fusion.
While WP Fusion can sync any data from WordPress to contact records in your CRM, it does not work 「auto-magically」 with every piece of data you see in your WordPress admin. That has to do with where your field data is stored.
We can break the kinds of data that WP Fusion syncs into three categories:

Data from the normal user tables – Works great with no extra setup
User data that』s in a different table – Requires some work
Data that』s calculated or not related to a specific user – Can be difficult

#Normal tables
WP Fusion can automatically detect and sync any data found in the wp_users and wp_usermeta database tables bidirectionally with any fields in your CRM.
Syncing data between just two tables (your users and your CRM) is automatic and requires no extra setup
These tables are the standard place where most plugins store data relating to a specific user. So even if WP Fusion doesn』t have a specific integration with a plugin, it』s likely the fields from that plugin will still show up under the Additional Fields section in the Contact Fields settings, and can be synced with your CRM without any extra work.
Note: To build the list of Additional Fields, for performance reasons WP Fusion only scans the usermeta of your own admin user. If you』ve just added a new field and it』s not showing, try saving some data in that field for your own admin user.
#User data that』s in a different table
Some plugins, like BuddyPress, store user profile data in different database tables.
When we talk about WP Fusion having an 「integration」 with a membership plugin (like the ones listed here), that means WP Fusion has additional code to:

Detect the available fields from that plugin』s custom tables, and list them in the Contact Fields in the settings
Extract the data from the custom tables and sync it to your CRM
Detect when data has been loaded from your CRM, and if that data belongs in a custom table, store it there

For example with BuddyPress, let』s say we have a custom XProfile field for Favorite Color, in the wp_bp_xprofile_data table. How that sync looks visually is something like:
Syncing data between your CRM and multiple WordPress tables can require some extra attention if using a non-supported plugin
And then in the code, that requires three functions:
#Detect the custom fields and list them for sync
Step one is figuring out which fields are available, and using the wpf_meta_fields filter to register them as available for sync.
With BuddyPress we make use of the bp_xprofile_get_groups() function, like
function example_prepare_buddypress_fields( $meta_fields ) {

// Get the field groups

$groups = bp_xprofile_get_groups( array(
'fetch_fields' => true,
) );

foreach ( $groups as $group ) {

foreach ( $group->fields as $field ) {

// Register the field in the list using the ID and label

$key = 'bbp_field_' . $field->id;

$meta_fields[ $key ] = array(
'label' => $field->name,
'type' => $field->type,
);

}
}

return $meta_fields;

}

add_filter( 'wpf_meta_fields', 'example_prepare_buddypress_fields' );
Which makes the fields show up for sync in the settings like this:

#Extract the data from the custom table and sync it to the CRM
When a user registers or a Push User Meta operation is run, WP Fusion tries to get all of the data it can out of the database for that user.
That data is then passed through the wpf_get_user_meta filter, which allows us to merge in data from different sources.
For example the code to load and sync the XProfile data would look like:
function example_get_buddypress_fields( $user_meta, $user_id ) {

$profile_data = BP_XProfile_ProfileData::get_all_for_user( $user_id );

// Get the profile data and merge it into the user_meta

foreach ( $profile_data as $field ) {
$key = 'bbp_field_' . $field['field_id'];
$user_meta[ $key ] = $field['field_data'];
}

return $user_meta;

}

add_filter( 'wpf_get_user_meta', 'example_get_buddypress_fields', 10, 2 );
#Load data from the CRM into the custom tables
Then, going the other direction, we want to make sure that data loaded from the CRM is properly stored in the custom database table, not the wp_usermeta table.
For that we make use of the wpf_set_user_meta filter. For example with BuddyPress, that code looks like:
function example_set_buddypress_fields( $user_meta, $user_id ) {

foreach ( $user_meta as $key => $value ) {

if ( strpos( $key, 'bbp_field_' ) === 0 ) { // If the field key starts with bbp_field_

$field_id = str_replace( 'bbp_field_', '', $key );

$field = new BP_XProfile_ProfileData( $field_id, $user_id );
$field->value = $value;
$field->save(); // Save the field to the wp_bp_xprofile_data table

unset( $user_meta[ $key ] ); // unset() the value so it's not saved to wp_usermeta

}
}

return $user_meta;

}

add_filter( 'wpf_set_user_meta', 'example_set_buddypress_fields', 10, 2 );
And there you have it. With those three code snippets, you can register and bidirectionally sync a user meta field from a custom database table.
#Data that』s not in a table
There may be some things you』d like to sync with your CRM that aren』t actually stored in any one place. Some examples:

Customer lifetime value
Most recently commented post
Most recent quiz score
Subscription renewal date

With things like this, they aren』t actually stored in any one place in the database that can be directly synced with your CRM, you』d have to write the code to calculate the values.
#Register the field
For example, let』s say you want to sync a WooCommerce customer』s lifetime value with your CRM. First register the field in the WP Fusion settings.
function example_prepare_ltv_field( $meta_fields ) {

$meta_fields['lifetime_value'] = array(
'label' => 'Lifetime Value',
'group' => 'woocommerce',
'pseudo' => true,
);

return $meta_fields;

}

add_filter( 'wpf_meta_fields', 'example_prepare_ltv_field' );
In this example we』ve set pseudo to true to indicate that the field doesn』t really exist. This is optional but it stops WP Fusion from loading the value back from your CRM, and filling up your database with unnecessary meta values.
#Calculate and sync the data
Similar to the BuddyPress example, we』ll use the wpf_get_user_meta filter to merge the custom value into the data that』s being sent to the CRM.
function example_sync_lifetime_value( $user_meta, $user_id ) {

$user_meta['lifetime_value'] = 0;

$customer_orders = get_posts( array(
'posts_per_page' => -1,
'post_type' => 'shop_order',
'post_status' => wc_get_is_paid_statuses(),
'meta_key' => '_billing_email',
'meta_value' => $user_meta['billing_email'],
'orderby' => 'ID',
'order' => 'DESC',
));

if ( ! empty( $customer_orders ) ) {

foreach ( $customer_orders as $order_id ) {

$order = wc_get_order( $order_id );

$order_total = $order->get_total();

$user_meta['lifetime_value'] += floatval( $order_total );

}
}

return $user_meta;

}

add_filter( 'wpf_get_user_meta', 'example_sync_lifetime_value', 10, 2 );
In this case, the code is quite a bit more complicated, since we』re not just pulling the data out from another part of the database. To calculate the lifetime value you first need to search for all orders placed by that customer, and then for each order increment the lifetime value field by that order』s total.
This also can introduce performance problems on stores with a large number of orders. In those cases you might want to cache the value using a transient, or create a separate meta key that tracks the customer』s LTV and is incremented with each new order.
#Examples
#Sync booking dates from multiple FooEvents products to different date fields in the CRM

#Sync subscription fields from multiple subscription products to their own fields
This example works with WooCommerce subscriptions, it registers each of your subscription products as a separate field on the contact fields list. For each you can sync the renewal date, status, and start date to a separate custom field in your CRM.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

The WP Fusion User Class

#Overview
As we discussed in the first section, WP Fusion achieves its flexibility and extensibility by standardizing the way WordPress communicates with different CRM systems.
The first section covered how to interface with your selected CRM directly by utilizing the wp_fusion()->crm object. Those methods are 「low level」, they require you to already know the contact ID of the contact you want to edit, and do very little in terms of validation of data or redundancy checking.
So while WP Fusion』s CRM class deals with contacts and contact data, the WPF_User class deals with WordPress users and user data.
This class works like a central dispatch, taking incoming events and data from our various plugin integrations and routing it to the appropriate method in your selected CRM.
#A basic example of how this all works, using LifterLMS

When a student completes a lesson in LifterLMS, LifterLMS triggers the 'lifterlms_lesson_completed' action.
In our LifterLMS integration file, we have a function attached to this hook. This function checks to see if any tags have been configured to be applied when the lesson is marked complete.
If there are tags to apply, the function then calls:
wp_fusion()->user->apply_tags( $tags, $user_id );

In the apply_tags() function, we first check to see if there is a contact ID available for that user. If the user doesn』t have a contact record, then nothing else happens.
Then we check the user』s current tags and see if the tags being applied are actually new. If the user already has the tag, then we don』t need to send an unnecessary API call.
Then apply_tags() sends the new tags to the CRM wrapper class (discussed in the previous article), by calling:
wp_fusion()->crm->apply_tags( $tags, $contact_id );

It checks the response from the API call, and if there were any errors, these are recorded in WP Fusion』s error log for troubleshooting purposes.
Finally we update the tags stored in in the usermeta table for that user, at '{crm_slug}_tags' so they can be quickly accessed again in the future.

#The available methods in the WPF_User class:

#user_register()

wp_fusion()->user->user_register( $user_id, $post_data = null, $force = false );
This function is triggered whenever a user registers on your site, from any plugin or other source. It can also be manually called to create a new CRM contact from an existing user ID.
Parameters:

$user_id (int) (Required) The ID of the user you』d like to use to create the new contact
$post_data (array) (Optional) You can pass in additional data you』d like to be included with the new contact. If this is left blank, WP Fusion will attempt to get as much data as possible out of the database
$force (bool) (Optional) If you have the setting for 「Create Contacts」 disabled in the WP Fusion settings, then you can set this argument to true to force creating a new contact.

Return values:

$contact_id (int) The contact ID of the new contact
false (bool) If there wasn』t enough data available to create a new contact, or if there was an API connection failure

#get_contact_id()

wp_fusion()->user->get_contact_id( $user_id, $force_update = false );
Gets the contact ID for a user from their local user meta, or forces an update of the contact ID by looking up their email address in your CRM.
Parameters:

$user_id (int) (Required) The ID of the user you』d like to get the contact ID for
$force_update (bool) (Optional) If set to true, this will force an update of the saved contact ID for the user by looking up their email address in your CRM

Return values:

$contact_id (int) The contact ID of the user
false (bool) If the user has no contact ID saved on the site, or if WP Fusion was unable to locate their email address in your CRM

#get_tags()

wp_fusion()->user->get_tags( $user_id, $force_update = false );
Gets the tags for a user from their local user meta, or forces an update of their tags by performing an API call.
Parameters:

$user_id (int) (Required) The ID of the user you』d like to get the tags ID for
$force_update (bool) (Optional) If set to true, this will force an update of the saved tags for the user by force-checking their contact ID and then re-loading the user』s tags from your CRM

Return values:

$user_tags (array) An array of tag IDs applied to the contact. Will be an empty array if no tags were found
false (bool) If the user has no contact ID saved on the site, or if WP Fusion was unable to locate their email address in your CRM

#pull_user_meta()

wp_fusion()->user->pull_user_meta( $user_id );
Loads the latest meta data from the CRM contact record for the specified user, and updates their saved data on your site.
Parameters:

$user_id (int) (Required) The ID of the user you』d like to load from the CRM

Return values:

$user_meta (array) An array of WordPress meta fields and their values that were loaded for the user
false (bool) If the user has no eligible meta to load, or if there was an error loading their contact record

#push_user_meta()

wp_fusion()->user->push_user_meta( $user_id, $user_meta = false );
Pushes meta data for a user from WordPress to your CRM.
Parameters:

$user_id (int) (Required) The ID of the user you』d like to update
$user_meta (array) (Optional) An associative array of WordPress meta keys and values to update. If left blank, WP Fusion will send all meta data found for that user in the database.

Return values:

true (bool) The contact was successfully updated
false (bool) If the user has no saved contact ID, or there was no eligible meta data to send

#apply_tags()

wp_fusion()->user->apply_tags( $tags, $user_id = false );
Applies an array of tags to a user.
Parameters:

$tags (array) (Required) An array of tag IDs to apply to the user
$user_id (int) (Optional) The user to apply the tags to. Will use the current logged in user if left blank

Return values:

true (bool) The tags were successfully applied
false (bool) If no contact ID was found for the user, or if the user already had the specified tags and no API call was needed

#remove_tags()

wp_fusion()->user->remove_tags( $tags, $user_id = false );
Removes an array of tags from a user.
Parameters:

$tags (array) (Required) An array of tag IDs to remove from the user
$user_id (int) (Optional) The user to remove the tags from. Will use the current logged in user if left blank

Return values:

true (bool) The tags were successfully removed
false (bool) If no contact ID was found for the user, or if the user didn』t have those tags in the first place

#import_user()

wp_fusion()->user->import_user( $contact_id, $send_notification = false, $role = false );
This function imports a contact from your CRM, by contact ID, and creates a new WordPress user. If a user already exists with the same contact ID, that user will just be updated.
New users will be given a randomly generated password. If you have enabled 「Return Password」 in the WP Fusion settings, this password will be stored back to their contact record.
Parameters:

$contact_id (int) (Required) The contact ID to import
$send_notification (bool) (Optional) Whether to send the new user the default WordPress welcome email
$role (bool / string) (Optional) If provided, the new user will be given the specified role. Otherwise they will be created with the site default role.

Return values:

$user_id (int) The ID of the new user (or existing user if updated)
$error (WP Error object) If there was an API error importing the user, or if the loaded contact data didn』t contain an email address

#Utility and helper functions:

#get_user_id()

wp_fusion()->user->get_user_id( $contact_id );
Looks up a user by their contact ID.
Parameters:

$contact_id (int / string) (Required) The contact ID to search by

Return values:

$user_id (int) The ID of the user
false (bool) If no user was found with that contact ID

#has_tag()

wp_fusion()->user->has_tag( $tag, $user_id = false );
Checks a given user to see if they have the specified tag.
Parameters:

$tag (int / string) (Required) The tag ID or tag label to check for
$user_id (int) (Optional) The user ID to check. Will default to the current user ID if left blank

Return values:

true (bool) The user has the tag
false (bool) The user does not have the tag

#get_tag_id()

wp_fusion()->user->get_tag_id( $tag_label );
For CRMs that use internal IDs for their tags (like Infusionsoft), this function will return the tag ID for a given tag label.
Parameters:

$tag_label (string) (Required) The tag label to check for

Return values:

$tag_id (int / string) The internal ID for the supplied tag label
false (bool) If no tag was found with that label

#get_tag_label()

wp_fusion()->user->get_tag_label( $tag_id );
For CRMs that use internal IDs for their tags (like Infusionsoft), this function will return the tag label for a given tag ID.
Parameters:

$tag_id ( int / string) (Required) The tag ID to check for

Return values:

$label (string) The tag label for that ID. If no tag is found, it will return 「Unknown Tag:」 with the tag ID

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

How To Submit A Job On Codeable For Custom Development

#Overview
Looking to expand the functionality of WP Fusion?
We』ve partnered with a team of skilled experts through Codeable to help you with your premium WordPress and WP Fusion development needs.
#What is Codeable?
Codeable is a trusted 3rd-party provider of vetted WordPress developers who can help you with any of your WordPress development needs. To ensure you』re matched with the right developer, they have a thorough application process to make sure you get the results you want.
#How to submit a job on Codeable for custom development
1. Go to our custom Codeable link and click the Get a Free Estimate button.

2. On the next page, you』ll be given two options. You can either Start a Project or Start a Consultation and speak directly with Codeable experts before starting your project.
For the purposes of this doc, we』ll be starting a new project. Click the Start a Project button to proceed.

3. The next page will allow you to enter the information for your project. First, select the type of project you need help with from the I need help with: dropdown.
The next page will allow you to enter the information for your project. First, select the type of project you need help with from the I need help with: dropdown.

Next, in the My: section, select Plugin from the dropdown if you need help customizing WP Fusion. If not, select the help you need.
Once ready, click the Continue button.

4. On the next page, you』ll be able to add details to your project including:

The project title.
The project description.
A URL.
Files and screenshots for extra information.
And you』ll be able to indicate if you want a specific expert to work on your project, or not.

5. Once happy, click Continue and move onto the next step.
6. On the next page, you』ll be able to indicate how complex and urgent your project is. Make your selection and you』ll see a rough estimate from Codeable. If you』re happy, click Continue.
 
7. Next, if you don』t already have one, you』ll be asked to create a Codeable account so that you can see the progress of your project and talk to developers.
8. Once ready, click Publish my Project and Codeable will get to work matching you with the right developers for the job.
#What happens next?
Once your project is submitted, you』ll be left in the capable hands of Codeable. Here』s some information from them to help:

Good luck with your project, we hope you get the results you』re looking for!

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

How to use a custom client ID for authentication

#Overview
With some CRMs, WP Fusion is registered as an app via those platforms』 developer programs. Because of this, you need an account on our site and a WP Fusion license to complete the initial authentication process with your CRM.
This applies to:

BirdSend
Drift
HubSpot
NationBuilder
Salesforce
Zoho

There may be scenarios where you want to use your own client ID for authentication, and not the WP Fusion client ID. For example if you have a created a custom branded app via your CRM』s developer program, or if you don』t have a WP Fusion license.
#Using a custom client ID and authorization URL
The client ID and client secret are public properties on each CRM』s integration class. You can override them by hooking into the wp_fusion_init_crm action, which passes the CRM object by reference.
For example with Zoho:
function set_custom_zoho_app( &$crm ) {

$crm->client_id = '1000.XXXXXXXXXXXXXXXXXXXXX';
$crm->client_secret_us = '08dccXXXXXXXXXXXXXXXXXXXXX';

}

add_action( 'wp_fusion_init_crm', 'set_custom_zoho_app' );
To override the initial authorization request URI for the 「Authorize」 button in the WP Fusion settings, use the wpf_{$crm}_auth_url filter, for example with Zoho:
function set_custom_zoho_auth_url() {

return "https://accounts.zoho.com/oauth/v2/auth?scope=ZohoCRM.modules.ALL,ZohoCRM.settings.ALL,ZohoCRM.users.READ,ZohoCRM.org.READ &response_type=code&access_type=offline&redirect_uri=https%3A%2F%2Fmysite.com%2Fzoho.php&prompt=consent&client_id=XXXX";

}

add_action( 'wpf_zoho_auth_url', 'set_custom_zoho_auth_url' );
Note that in this example you must have registered https://mysite.com/zoho.php as the redirect URI for your app, and must have a script running at that location which is capable of listening for the authorization response and redirecting back to the WP Fusion settings page with the &code= parameter in the URL.
#Salesforce example
To set your own custom Salesforce client ID and secret:
function set_custom_salesforce_app( &$crm ) {

$crm->client_id = '3MVG9CEn_O3jvv0xMf5rhesocm_5czidz9CFtu_qNZ2V0Zw.bmL0LTRRylD5fhkAKYwGxRDDRXXXXXXXXXXXX';
$crm->client_secret = '9BB0BD5237B1EA6ED8AFE2618053XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX';

}

add_action( 'wp_fusion_init_crm', 'set_custom_salesforce_app' );
To override the initial OAuth authorization URL:
function set_custom_salesforce_auth_url() {

$args = array(
'client_id' => wp_fusion()->crm->client_id,
'redirect_uri' => rawurlencode( admin_url( 'options-general.php?page=wpf-settings&crm=salesforce' ) ),
'response_type' => 'code',
'scope' => 'api%20refresh_token%20offline_access',
);

$url = add_query_arg( $args, 'https://login.salesforce.com/services/oauth2/token' );

return $url;

}

add_action( 'wpf_salesforce_auth_url', 'set_custom_salesforce_auth_url' );

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No