Support for GraphQL aliasing will be removed on October 15, 2026. After this date, API requests that use aliases may return errors.

What are GraphQL aliases?

GraphQL aliases allow you to assign a custom name to a field within a query. They are commonly used to request the same field multiple times in a single API request.

For example:

query {
  firstPost: post(id: "123") {
    id
    title
  }

  secondPost: post(id: "456") {
    id
    title
  }
}

In this example, the aliases firstPost and secondPost allow two different posts to be returned within a single query.

Who is affected?

This change only affects customers who use GraphQL aliases in:

• Custom applications

• API integrations

• Scripts

• Middleware

• Other custom implementations that connect to the Bettermode GraphQL API

If your API requests do not use GraphQL aliases, no action is required.

What do I need to do?

If your implementation uses GraphQL aliases, you'll need to update those requests before October 15, 2026.

In most cases, this means replacing a single aliased query with separate API requests.

For example, instead of retrieving multiple posts within a single aliased query, you should send one request for each post.

We recommend completing any required changes by October 1, 2026. This gives your team additional time to test your integrations before support is removed.

Why is this change being made?

Removing support for GraphQL aliases is part of our ongoing effort to improve the security and reliability of the Bettermode API.

Need help?

If you have questions about this change or how it affects the Bettermode platform, please contact our Support team.

For implementation guidance and API reference material, we recommend reviewing the related developer documentation below.

Check out Bettermode’s Developer's Guide to learn more about Bettermode’s GraphQL.

Other articles you might be interested in:

• Bettermode's Support Scope

• Get started with GraphQL API Tutorials

• Getting Started with GraphQL Developer's Guide

To integrate your Bettermode site with Salesforce 360, you need the following items:

1. Admin access to Salesforce is required.

2. Admin access to Bettermode is also required.

3. The Salesforce 360 app enabled for your community — contact the Bettermode team if you don't see it on your App store —> Apps & Integrations page.

4. You need to add a callback URL in Salesforce (provided below).

5. Consumer Key & Secret from your Salesforce External Client App.

💡 We highly recommend connecting to a Salesforce sandbox first to validate the integration before connecting your production org — the connect form lets you choose the environment.

Part 1: Create an External Client App in Salesforce

1. Log in to your Salesforce org and click the gear icon in the upper-right corner, then select Setup.
   

   

2. In Setup, search for "Platform Tools" on the left side and click External Client App Manager under Apps, then click New External Client App on the top-right.
   

   

3. Add an app name (e.g., Bettermode Salesforce 360) and press tab so the API name fills automatically.

4. Add your email.

5. Tick the box next to API (Enable OAuth Settings) and insert the Callback URL and scopes.

   Callback URL: https://salesforce360.bettermode.app/salesforce/callback 

6. Add OAuth Scopes:

   1. Manage user data via APIs (api)

   2. Perform requests at any time (refresh_token, offline_access)

      

7. Click Create and wait up to 5 minutes for Salesforce to finish provisioning the app.

8. Open your app in External Client App Manager and click Settings —> OAuth Settings —> Consumer Key and Secret (you may need to complete 2-factor authentication). Copy the Consumer Key and Consumer Secret — you'll need both in Part 2.

   

Part 2: Connect Salesforce 360 in Bettermode

1. Log in to your Bettermode account, go to Administration view and navigate to the App store section.

2. Go to Apps & Integrations page

3. Click on Salesforce 360 and click Install.

   

4. In the app's settings, fill in the connection form:

• Environment — choose Production or Sandbox (Sandbox uses test.salesforce.com)

• Salesforce Consumer Key (Client ID) — from Part 1

• Salesforce Consumer Secret — from Part 1 (stored encrypted and only used to connect to your Salesforce org)

The Connect button stays disabled until both credentials are entered.

Click Connect — you'll be redirected to Salesforce. Log in and complete 2-factor authentication if enabled, then review the requested permissions and click Allow.

💡 When logging in to a sandbox, remember that your sandbox username includes a suffix after your email (e.g., you@company.com.sandboxname).

5. After authorizing, you'll be redirected back to the Salesforce 360 settings page, where you can choose which spaces sync to Salesforce and configure field mappings.

💡 No profile fields are synced until you explicitly map them. Each field mapping is one-directional — you choose per field whether it syncs Bettermode → Salesforce or Salesforce → Bettermode.

The integration between Salesforce 360 and Bettermode is now set up. Salesforce 360 will provision three custom objects in your org — Bettermode Community Members, Bettermode Community Posts, and Bettermode Community Activities — along with a read-only permission set (Bettermode Salesforce 360 User) and default list views.

What syncs to Salesforce

💡 Salesforce's "Recently Viewed" list view can appear empty even when records exist — switch the list view to "All Bettermode …" to see synced data.

To surface this data on Account and Contact pages and grant access to your team, your Salesforce admin needs to assign the permission set and add the related lists to page layouts.

Related

1. Granting Access to Exported Data: Bettermode Site and Salesforce Integration

2. Create Salesforce Cases from the Bettermode Site

3. Exporting Data from Site to Salesforce