We shipped a lot this summer, and the one I keep coming back to is this: your community is now something Claude and other AI assistants can read and act on through MCP.

Here's what's new, and why each piece matters.

AI tool connectivity through MCP

Your community now speaks MCP, the standard interface AI assistants use to read and act on external systems. Point Claude or another assistant at your community and it can pull what it needs, or take action, with no custom integration first. We'll demo live workflows on the call.

A first look at community agents

The Moderation Agent is live in beta today, working the queue with you. Two more are coming: a Community Builder Agent that sets up a community through conversation, and an Engagement Agent that surfaces the members worth re-engaging before they go quiet.

HubSpot 360, now in beta

Community engagement lands directly on your HubSpot contacts, companies, and deals, so member activity sits next to email opens and deal stages. The CSV export you've kept to answer “is the community doing anything” can go away.

Salesforce 360, now in beta

Posts, joins, replies, RSVPs and attendance flow into Salesforce as three native objects, and reps see community activity right on the contact record. Profile fields sync back the other way.

Analytics 2.0

Analytics rebuilt from the ground up for speed and accuracy across members, content, and engagement, and the foundation for tying engagement to pipeline. We'll show where that stands on the 27th.

What's next

This release is mostly connective tissue, getting community data to where decisions already get made. The agent layer is where we go next, and the foundation we laid this summer is what makes it possible.

You'll need admin access to Bettermode and a HubSpot user who can install apps (Super Admin, or the App Marketplace Access permission).

Part 1: Connect HubSpot

1. In your Bettermode Administration view, go to App store → Apps & Integrations.

2. Click HubSpot 360, then click Install. Contact the Bettermode team if you don't see the app.

3. In the app's settings, click Connect HubSpot. You'll be redirected to HubSpot.

4. Log in, pick the portal you want to connect if your user has more than one, review the requested permissions, and click Connect app.

5. You're redirected back to the HubSpot 360 settings page. That's the whole connection! The sync, ticket, field mapping, and Knowledge Base options are now unlocked.

💡 If you have a HubSpot test portal, connect that first and validate everything before connecting production. Disconnecting and reconnecting to a different portal takes a minute.

Part 2: Turn on sync

1. On the settings page, switch on Enable sync.

2. The first time you enable it, HubSpot 360 runs a one-time backfill of your existing members. You can watch the progress on the settings page; how long it takes depends on the size of your community.

3. From then on, member changes reach HubSpot within seconds, and a reconciliation pass runs every half hour to catch anything a missed event left behind.

What lands in HubSpot

Members sync as standard Contacts, matched by email and associated to existing Companies by email domain. Each synced contact carries six properties in a Bettermode property group: member ID, member name, joined at, last seen at, spaces, and badges.

To see them, open any contact and search the property list for "bettermode", or filter a contact view by Bettermode member ID is known to list every synced member.

Part 3: Map member fields to contact properties

A field mapping is a link between one member profile field in Bettermode and one contact property in HubSpot. Once two fields are linked, HubSpot 360 keeps them in sync automatically: when the value changes in the source system, the other side gets updated on the next sync.

1. On the settings page, find Field mappings and click Add mapping.

2. Pick a Bettermode member field on one side and a HubSpot contact property on the other.

3. Choose the direction. Each mapping is one-directional: Bettermode → HubSpot or HubSpot → Bettermode, decided per field.

4. Click Save. New mappings backfill existing members on the next pass, so you don't need to re-run anything.

Part 4: Create HubSpot tickets from posts

Some community questions need to become support tickets. This puts a Create a HubSpot ticket option in the (…) menu of every post (visible to staff only).

1. On the settings page, switch on Enable ticket creation.

2. Navigate to any post, click the (…) menu at the top right, and click Create a HubSpot ticket.

3. Fill in the ticket details. You can search your HubSpot contacts to attach the right one.

4. Click Create ticket. The ticket is created in HubSpot with the post's context attached.

Part 5: Search your Knowledge Base from the community

If your portal has a HubSpot Knowledge Base (Service Hub Professional or Enterprise), federated search can surface its articles inside community search.

1. On the settings page, switch on Enable Knowledge Base search.

2. Search the community for a phrase you know appears in an article. Knowledge Base results appear alongside community results.

For example, you can ask:

“Which spaces had no new posts in the last 7 days?”

Your AI tool calls the appropriate Bettermode tools to retrieve the answer. With your approval, it can also take supported actions, such as publishing a post, sending a direct message, assigning a badge, or hiding spam.

The MCP server is available to admins only and excludes destructive actions by design. It cannot delete spaces, members, or your community, or change a space from public to private.

Every action runs under a real member identity. This means posts and messages created through your AI tool appear as if they were created by the admin associated with the connector.

Key Concepts

Before setting up a connection, it helps to understand how Bettermode uses MCP:

MCP (Model Context Protocol) — An open standard that lets AI tools connect to external products. Claude, ChatGPT, and Cursor support MCP.

Connector — The connection between your AI tool and your Bettermode community. Each connector has a scope—read-only or read + write—and a token tied to the admin who authorized it.

Read tools — Tools that retrieve community data, such as spaces, posts, members, badges, and analytics, without making changes.

Write tools — Tools that make changes to your community, such as creating a post, sending a direct message, assigning a badge, adding members to a space, or hiding a post. Each write requires your approval.

Acting identity — The member identity the connection uses when performing actions. You can ask your AI tool to call bettermode_whoami to verify the acting member and connector scope.

Before You Start

Before connecting an AI tool to Bettermode:

• You need admin access to your community.

• Your AI tool must support custom MCP connectors.

• MCP is available on all plans.

• Starter is limited to 10 MCP requests per day per connector.

• Growth and Premium have unlimited MCP usage within the standard API rate limits.

Connect an AI Tool to Bettermode

1. Go to Administration → App store → MCP.

2. Copy the connection URL. There is nothing to generate on the Bettermode side. Bettermode automatically selects the correct region based on your community's data residency:

   • US communities use https://mcp.bettermode.com/

   • EU communities use https://mcp.bettermode.de/

3. In your AI tool, go to Settings → Connectors → Add custom connector, paste the connection URL, and authorize the connection.

4. Choose the scope during authorization. The scope is selected in your AI tool's authorization flow, not in Bettermode:

   • Read-only: Lets the AI tool retrieve community data without making changes.

   • Read + write: Lets the AI tool retrieve data and perform supported actions under your identity.

5. Configure the tool permissions:

   • Set read tools to Always Allow.

   • Set write tools to Needs Approval.

Your AI tool can now access the Bettermode tools available to the connector's scope.

Important: A read + write connector performs actions under the identity of the admin who authorized it.

Read Tools

Read tools retrieve information from your community without making changes. You can use them to work with spaces, posts, members, badges, post types, and analytics.

Write Tools

Write tools make changes to your community and are available with a read + write connector. Your AI tool asks for approval before each write.

Example: From Question to Action

You can combine read and write tools to retrieve information and then take action based on the results.

For example, ask:

“Find members who joined in the last 30 days and haven't posted, then send each a personalized check-in DM.”

Your AI tool can then:

1. Call bettermode_list_members and filter by join date.

2. Cross-check each member's activity.

3. Draft a personalized message for each member.

4. Call bettermode_send_message for each member.

Because sending a direct message is a write action, your AI tool asks for your approval before each message is sent.

Safeguards and Limits

The MCP server includes safeguards that limit what connected AI tools can do in your community:

• Per-action approval: Every write tool call requires confirmation in your AI tool before it runs.

• No destructive tools: The MCP server cannot delete spaces, members, or your community, or change a space from public to private.

• One target per write: Direct messages and badge assignments apply to one member per call. For bulk actions, this surfaces one approval per member rather than one approval for the entire action.

• Reversible moderation: Hiding a post is the strongest supported moderation action, and a hidden post can be unhidden.

• Bounded queries: Analytics queries can cover up to 186 days per request. If a request is refused, try a shorter date range.

• Paginated results: List tools return up to 50 items per page.

• Rate limits: MCP requests count against a dedicated MCP balance and are subject to your plan's API rate limits.

Data Residency

The MCP server automatically matches your community's region.

Bettermode determines the region from your connector and routes requests to the in-region API. This means EU community data never transits a US process on the Bettermode side.

Data returned to the connected AI tool leaves Bettermode. Claude, ChatGPT, and Cursor are third-party services, and most are US-hosted.

FAQs and Troubleshooting

Why can't my AI tool perform a write action?

Check the connector scope. A read-only connector can retrieve information but cannot make changes to your community. Write tools require a read + write connector.

How do I check which member and scope my connection is using?

Ask your AI tool to call bettermode_whoami. It returns the member the connection acts as and its scope.

Why did my analytics request fail?

Analytics queries can cover up to 186 days per request. If your request exceeds this range, try a shorter date range.

Why am I not seeing all the results?

List tools return up to 50 items per page. Your AI tool may need to retrieve additional pages for larger result sets.

What happens if I reach the MCP request limit?

Starter is limited to 10 MCP requests per day per connector. Growth and Premium have unlimited MCP usage within the standard API rate limits.

How do I disconnect an AI tool?

Go to Administration → App store → MCP and revoke the connector. Revoking it immediately disconnects the connected AI tool.

Related Articles

• API Rate Limits

• How to install and uninstall apps on Bettermode

• Bettermode's Developer's Guide.

The Bettermode MCP server is live on every plan. Connect your community to an AI tool and you can ask it questions in plain language, then let it act on the answer with your approval. Here's what it does and how to switch it on.

Ask your community a question

MCP is an open standard that lets AI tools connect to other products. Anything that speaks it can connect, so this is not a Claude integration or a ChatGPT integration, it is one connector that serves all of them. Once you've connected your community, you stop clicking through dashboards to find things out and just ask.

"Which spaces had no new posts in the last 7 days?" Your AI tool calls the Bettermode tools it needs, reads the answer out of your community, and tells you. Same for "who joined this month and hasn't posted yet", or "how did engagement trend last quarter". There are eleven read tools covering spaces, posts, members, badges, post types, and analytics, and your AI tool picks the ones the question needs.

Ask for a chart and you get one, drawn in the conversation rather than exported from a dashboard.

Then act on it, one approval at a time

Reading is half of it. A read and write connector can also publish a post, send a direct message, assign a badge, add existing members to a space, or hide a post.

Every one of those asks you first. Your AI tool shows you exactly what it's about to do and waits for your OK, per action, so a request like "message each of the 12 quiet members" surfaces twelve approvals rather than one blanket yes. It's slower on purpose. You keep the final call on anything that shows up in your community.

What it can't do

The MCP server is admin only, and we left the destructive tools out of it on purpose. It can't delete spaces, members, or your community, and it can't flip a space from public to private. Hiding a post is the strongest moderation action available, and you can unhide it.

One thing to know going in: every action runs under a real member identity. Posts and messages created through your AI tool appear as the admin who set the connection up, not as a bot. Ask your AI tool to call bettermode_whoami any time you want to confirm which member you're acting as and whether the connector is read only or read and write.

Your data stays in its region

Bettermode routes MCP requests to the API in your community's region, so EU community data never passes through a US process on our side. US communities connect through mcp.bettermode.com and EU communities through mcp.bettermode.de, and the URL you copy already points at the right one.

Worth being straight about the other half: whatever your AI tool reads leaves Bettermode at that point. The AI tools themselves are third party services and most are hosted in the US.

Somewhere to start

If you want prompts to paste in on day one:

- "What happened in the community this week?" gets you a digest worth pasting into a standup.

- "Who joined in the last 30 days and hasn't posted yet?" before you write the re-engagement email.

- "Is there any spam from the last day? Hide it." as a morning sweep.

- "Who replied the most in Product feedback this month?" when you're deciding who to recognize.

The first one is read only, so it costs you nothing to try before you ever hand over a write scope.

How to turn it on

Go to Administration > App store > MCP and copy your community's connection URL. That's the whole job on our side, there's nothing to generate.

The rest happens in your AI tool. Go to Settings > Connectors > Add custom connector, paste the URL, and authorize it. The scope lives in that authorization step, so read only or read and write is a decision you make in the auth flow rather than on the Bettermode side.

Once you're connected, we'd set the read tools to always allow and leave every write tool on needs approval. That's the setup that makes this pleasant to use without ever letting it surprise you. You can revoke access from the same MCP page whenever you want, and the AI tool disconnects immediately.

Plans and limits

MCP is available on all plans. Starter gets 10 MCP requests per day per connector. Growth and Premium are unlimited within the standard API rate limits. Analytics queries cover up to 186 days at a time, and list tools return 50 items per page, so a long-range question may take your AI tool a few calls.

Full setup steps, the complete tool list, and troubleshooting are in the MCP guide.

Watch me run it live on August 27

MCP is the piece of this summer's release that's hardest to describe and easiest to get once you watch it work, so I'm demoing it end to end at the Summer Product Update on Thursday, August 27 at 2:00 PM ET. Real connector, real community, including the write path and what the approval step actually looks like when it stops you.

Bring the question you'd want to ask your own community and I'll try it live in the Q&A. RSVP below, and the recording goes out afterward if you can't make it.

What's next

This is v1, and the tool list is where it'll grow first. Connect it, point it at something you'd normally do by hand, and tell us in the replies what it couldn't reach. That's the feedback that decides which tools we add next.

We've been heads-down all summer, and this is the release I've been most impatient to talk about.

Most of what we shipped answers one question we hear constantly: what is the community actually worth, and why does the answer live in a different tool than the rest of your revenue data? This release closes that gap. Community activity now lands in the CRM your team already works in, analytics got rebuilt underneath, and your community became something AI assistants can read and act on.

HubSpot 360, now in beta

Community engagement lands directly on your HubSpot contacts, companies, and deals. Member activity sits next to email opens and deal stages, so you can build lists and workflows off community behavior the same way you would off any other signal.

The practical version: the CSV export you've been maintaining to answer “is the community doing anything” can go away.

Salesforce 360, now in beta

Posts, joins, replies, RSVPs and attendance flow into Salesforce as three native objects: Community Member, Community Post, and Community Activity. Reps see community activity right on the Contact record, and your staff can raise a Case from a post without leaving the thread.

Profile fields sync back the other way, so the community knows what the CRM knows about a member.

Analytics 2.0

We rebuilt analytics from the ground up for speed and accuracy across members, content, and engagement. The old version got slow as communities grew, and slow analytics is analytics nobody opens.

This is also the foundation for tying engagement to pipeline, which is the report most of you have been asking us for. We'll show where that stands on the 27th.

AI tool connectivity through MCP

Your community now speaks MCP, the standard interface AI assistants use to read and act on external systems. In practice that means you can point Claude or another assistant at your community and have it pull what it needs, or take action, without anyone building a custom integration first.

We'll demo live workflows on the call. This is the piece that's hardest to explain and easiest to understand once you watch it run.

A first look at community agents

The Moderation Agent is live in beta today. It works the queue with you rather than around you, and it's the first of a layer we're building out.

Two more are coming. A Community Builder Agent that sets up and configures a community through conversation, and an Engagement Agent that surfaces the members worth re-engaging before they go quiet. We'll show where both are headed.

What's next

This release is mostly about connective tissue: getting community data to where decisions already get made. The agent layer is where we go next, and the foundation we laid this summer is what makes it possible.

If you're already on Bettermode and want early access to the HubSpot 360 or Salesforce 360 betas, come ask during the Q&A. That's the fastest way in.

As always, tell us what's working and what isn't. It shapes what we build.

Know who you're actually talking to

A Contact record is supposed to tell you everything about a customer. Today it stops at the edge of your community.

Salesforce 360 creates three custom objects in your org and keeps them current: Bettermode Community Member, Bettermode Community Post, and Bettermode Community Activity. Joins, posts, replies, RSVPs, and event attendance roll up under the Account and Contact they belong to. Every rep opening that record sees the full picture, and every segment you build in Salesforce can use community behavior as a signal.

Your CRM and your community, in agreement

Profile data stays in sync. Map any Bettermode member field to any Salesforce Contact field and pick the direction per field. Updates in Bettermode reach Salesforce within seconds, changes in Salesforce flow back on a regular sync, and empty values are always skipped, so a blank never overwrites good data on either side.

Answers already exist. Put them where people ask.

Federated search brings your Salesforce Knowledge base into the community. A member asks a question and finds the article that answers it, without leaving the thread and without waiting on your team.

Escalate without leaving the post

Some questions do need a human. Staff members get a Create a Salesforce Case option in the (…) menu on every post. Turn on Enable Case Creation, map your Bettermode fields to your Salesforce case fields, and a community question becomes a case with the post's context already attached.

How to turn it on

Go to App store → Apps & Integrations, open Salesforce 360, and click Install. You'll need admin access on both sides and a Consumer Key and Secret from a Salesforce External Client App. Full steps are in the Salesforce 360 setup guide.

What's next

Next we're building revenue influence, so you can see which accounts had members active in the community before a deal closed. Deeper analytics and more mappable objects come after that.

Once you've connected your org, tell us in the replies how the first sync goes. If you need another object or field mapped, ask here. That list is what we build from.

Salesforce 360 connects your Bettermode site to your Salesforce org so community engagement shows up where your revenue and support teams already work. Members, posts, and activity sync into Salesforce as native records that appear on Account and Contact pages, and your staff can open Salesforce cases straight from a community post.

What you can do with it

• See community activity on the customer record. Joins, posts, replies, RSVPs, and event attendance sync to Salesforce and roll up under the Account and Contact they belong to.

• Spot engagement trends. Combine community engagement with the customer data already in Salesforce to find patterns you would otherwise miss.

• Build targeted segments. Use community activity to drive personalized campaigns and engagement workflows for specific customer groups.

• Create cases from posts. Staff members get a Create a Salesforce Case option in the (…) menu on every post, so a support question in the community becomes a case without switching tabs.

Before you start

• Admin access to Salesforce, or an admin who can create an External Client App and assign permission sets for you.

• Admin access to Bettermode.

• The Salesforce 360 app enabled for your site. Check App store → Apps & Integrations.

💡 We highly recommend connecting a Salesforce sandbox first to validate everything before you point the app at your production org. The connect form lets you pick the environment.

Setup path

Work through these in order. Steps 3 and 4 are optional, but most teams want both.

1. Integrate Salesforce with Bettermode Site — create the External Client App in Salesforce, then connect it in Bettermode and choose which spaces sync. Everything else depends on this.

2. Exporting Data from Site to Salesforce — turn on the Enable Site data export toggle and confirm the custom objects exist in your org.

3. Granting Access to Exported Data — assign the Bettermode Salesforce 360 User permission set so your team can actually see the synced records. Skip this and the data is there but invisible to everyone except admins.

4. Create Salesforce Cases from the Bettermode Site — enable case creation and map your fields so staff can raise cases from posts.

What Salesforce 360 creates in your org

Connecting the app provisions three custom objects, a read-only permission set, and a default list view for each object.

Good to know

• Nothing syncs until you choose it. You pick which spaces sync, and no profile fields are mapped by default. Each field mapping is one-directional, so you decide per field whether it flows Bettermode → Salesforce or Salesforce → Bettermode.

• Your consumer secret is stored encrypted and is only used to connect to your Salesforce org.

• Records exist even when a list view looks empty. Salesforce's "Recently Viewed" view is often blank on new objects. Switch to the matching "All Bettermode …" view.

• Surfacing data on Account and Contact pages is a Salesforce-side task. Your admin needs to add the related lists to the page layouts after the permission set is assigned.

All Salesforce 360 articles

1. Integrate Salesforce with Bettermode Site

2. Exporting Data from Site to Salesforce

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

4. Create Salesforce Cases from the Bettermode Site

Locale groups: one space per language

Localization is built on locale groups. You enable it on a space, pick that space's language, and it becomes the primary. From there you add a locale variant for each language you want to support, and every variant is its own space with its own content, members, and permissions. The group keeps them connected under one shared URL structure, so a group with the base path docs gives you /en/docs, /de/docs, and so on.

Members land in their own language

To a member, a locale group shows up as a single space in the navigation, not one entry per language. Open the base path and you're sent to the space that matches your language. Internal links keep you in that language as you move around, and you can switch languages any time from the nav bar or your account settings. Spaces without a dedicated locale stay visible to everyone.

Built for regional teams

Because each locale is a real space, your regional teams can run their own. They get their own moderators and permissions, and they can publish content that fits their market instead of forcing one translation on everyone. Post types stay in sync across the group, so the structure stays compatible and your content stays portable between languages.

What it doesn't do yet

Localization doesn't auto-translate your content. You publish what fits each market, so you stay in control of what every region sees. If AI-assisted translation is what you're after, that's on the roadmap (more below). v1 is the routing and structure that make a real multi-language community work in the first place.

How to turn it on

Go to Administration > Settings > Localization to manage your community languages.

Then open any space, find the Locales tab, and select Enable localization. Name the group, set the primary language, and start adding locales. The base path is the shared URL path every locale in the group lives under.

The number of languages you can enable depends on your plan. Full steps are in the localization guide.

What's next

This is v1. We're already building AI-assisted translation with a review step before anything publishes, so you'll be able to scale content across languages without handing over editorial control.

Give it a try and tell us how it goes in the replies. If something's missing for your use case, that's exactly the feedback that shapes what we ship next.

Localization does not translate content automatically. Each locale space is managed separately, so you can publish content that fits specific market.

Key concepts

Locale group — A set of spaces linked together as language variants of each other. Every group has one primary Space and any number of locale variants.

Primary space — The space you enable localization on. It becomes the source for new locale variants and represents the group in your community's navigation.

Locale variant — A space added to the group for a specific language. Each language can have only one space per group.

Base path — The shared URL path for every space in the group. Each Space lives at locale/base-path. For example, with the base path docs, your English Space lives at /en/docs and your German Space at /de/docs.

Before you start

Locale groups use the languages enabled for your community. Go to Administration > Settings > Localization to manage your community languages. The number of languages you can enable depends on your plan.

Enable localization on a Space

1. Open your Administration panel and select the Site > Space.

2. Go to the Locales tab in the space settings top right corner.

3. Click Enable localization

4. Enter a Locale group name. It is pre-filled with the space name.

5. Select the Primary space locale — the language of this space's existing content.

6. Select Enable localization.

This creates a Locale group with your space as the primary. You can now add locale variants.

Add a locale

1. In the space's locales settings, find the locales tab and select “Add locale”. You can also select Add locale under the primary Space in the site tree.

2. Select the language. Languages already used in the group are not available — each group can have one space per language.

3. Optionally, enter a name for the new space. It defaults to the primary space's name.

4. Select Add.

The new space is created as a locale variant of the primary space, ready for content in that language.

Manage a Locale group

The Locales > Configuration > Settings tab of any space in the group shows the group settings:

• Name and description — How the group appears in your admin tools.

• Base path — The shared path for every locale. Changing it updates the URL of all member spaces at once.

How members experience localized Spaces

• One entry in the sidebar. A Locale group appears as a single item in the navigation, so members see one space that is relevant to their selected language, not one per language.

• Language-aware URLs. Each locale space has its own URL, such as /en/docs or /de/docs. Members who open the base path (/docs) are redirected to the space that matches their language.

• Language switching. Members change their language from the navigation bar or via their account settings. The community then serves the locale spaces that match their selection.

• Spaces that don’t have a dedicated locale are shown to all users.

Remove a locale or delete a group

• Remove a locale variant. In the Locales > Configuration > Locales tab, select the remove icon next to the variant. This unlinks the space from the group. The Space and its content are not deleted. The primary Space can't be removed.

• Delete the group. Select Danger zone > Unlink group in the Localization settings. This unlinks all member spaces. The spaces themselves are not deleted.

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