Bettermode

Manage a Bettermode community through its GraphQL API. Agents publish and edit posts, add comments and reactions, read members and spaces, manage tags, and reach any uncovered part of the schema with a generic GraphQL action.

14 actions API key available

Bettermode website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A product release ships and the release notes land in the launch workflow

List Spaces resolves the announcements space by slug so the post targets the right audience

Create Post drafts the community announcement with the release title and a body written for members, not changelogs

The community manager reviews the draft in place, edits tone if needed, and approves publication to the whole community

The post goes live and the returned URL fans out to the internal launch channel

List Posts and Get Post sweep the announcement over the next days for reply and reaction counts

Create Comment answers the routine questions with linked documentation

Unanswered or heated threads escalate to the product team with the full context

What This Integration Enables

A community is the one channel where your customers talk back in public, which makes automating it different from automating a mailing list: every write is visible to everyone, attributed, and remembered. Bettermode exposes the whole community as a GraphQL schema, and this connector puts agents to work on it with that visibility in mind. FlowRunner agents publish and edit posts, thread comments, add reactions, read members and spaces, and reach any uncovered corner of the schema through a generic GraphQL action. - Cross-post product announcements and blog content into the right space, on schedule - Sync new members into the CRM and mailing list with profile and role data - Run engagement workflows: react, comment, and surface threads that need a human - Pull posts, members, and reaction counts into reporting pipelines - Execute arbitrary GraphQL queries and mutations for anything the dedicated actions do not cover Because everything an agent does here happens in front of members, FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates sit on the public-facing writes: publication gets a review, and deletion gets a decision.

Without FlowRunner

Announcements arrive late or never Cross-posting releases to the community depends on someone remembering after the real launch work

Member data stays in the community Sign-ups, roles, and activity never reach the CRM, so community members are invisible to revenue teams

Moderation is delete-first Cleanup happens fast and unlogged, and members notice when their words vanish

With FlowRunner

The community is a launch channel Every release posts to the right space on schedule, reviewed by a person before it reaches members

Members sync everywhere New sign-ups flow to the CRM and mailing list with role and status attached

Removal is a reviewed decision Delete proposals carry the post, the author, and the reason, and a moderator makes the call

Use Case Scenarios

The launch that always includes the community

The release workflow that updates the changelog and emails customers also calls Create Post into the announcements space, targeted by Post Type ID as a discussion. The community manager approves the draft, the post publishes, and [Slack](/integrations/slack) tells the team it is live with the post URL. Update Post handles the inevitable correction without a delete-and-repost that would orphan early comments.

Members become known to revenue

Nightly, List Members pages through the community with the cursor, picking up new sign-ups since the last run. Each new member syncs to [HubSpot](/integrations/hubspot) as a contact with username, email, and role, so when a support ticket or a sales conversation starts, the team can see the person is an active community voice. Get Member enriches on demand when a workflow needs one profile rather than a page.

Engagement reporting without the dashboard tour

Weekly, List Posts pulls each space's recent activity and logs title, author, reaction count, and reply count to [Google Sheets](/integrations/google-sheets). Threads with high replies and no team response surface in the community channel for a human answer. When the report needs something the dedicated actions do not return, Run GraphQL Query fetches it directly from the schema, one query instead of a feature request.

Human-in-Loop Highlight

Delete Post permanently removes a member's own words from your community, and the member will notice. There is no undo in the API and no undo in the relationship: a false-positive spam deletion tells a real customer their contribution was trash. So moderation agents on this page flag, never fire. The agent posts the case to the moderation channel: "Post 'Selling my conference ticket' in General by member m_2481, joined 3 days ago, matches the marketplace-spam pattern. Body and author profile attached. Delete, or move and warn?" A moderator decides, the action executes, and the decision logs with their name. The same gate covers mutations sent through Run GraphQL Query, because an escape hatch into the full schema is exactly the place where an unreviewed write can do community-wide damage.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

14 actions

Members

List Members Retrieves members with cursor pagination and optional free-text filtering, returning id, name, username, email, role, and status. The sweep behind CRM syncs.
Get Member Retrieves a single member's profile by ID, including tagline, picture, role, and status. The enrichment step when one record matters.

Spaces

List Spaces Retrieves the community's spaces with id, name, slug, privacy setting, and member count. The resolution step before posting anywhere.
Get Space Retrieves one space's details including member and post counts. Used to verify a target before publication.

Posts

List Posts Retrieves a space's posts, most recent first, with cursor pagination: title, plain-text body, author, reaction and reply counts. The raw material for engagement reporting.
Get Post Retrieves a single post in full, including tags and timestamps. The context pull before a moderation or escalation decision.
Create Post Publishes a post in a space with title, body, and optional Post Type ID. Returns the live post's id and URL. Reviewed before release, because the whole community reads it.
Update Post Updates a post's title or body, leaving omitted fields unchanged. The correction path that preserves the thread.
Delete Post Permanently deletes a post. Cannot be undone, which is why it sits behind this page's moderation gate.

Comments

Create Comment Adds a threaded reply to a post. The action behind automated answers and acknowledgments that still read like the team showed up.

Reactions

Add Reaction Adds an emoji reaction, a common one or a custom key, to a post. The lightest-touch engagement signal.
Remove Reaction Removes a previously added reaction using the same key. Keeps automated engagement reversible.

Advanced

Run GraphQL Query Executes arbitrary GraphQL queries or mutations against the full Bettermode schema with variables, returning the raw data object. The escape hatch, and for mutations, a gated one.

Frequently Asked Questions

What can FlowRunner do with Bettermode?

FlowRunner agents can run List Members, Get Member, and List Spaces in Bettermode, plus 11 more actions.

Does connecting Bettermode to FlowRunner require OAuth?

No. Bettermode connects to FlowRunner with an API key, no OAuth flow required.

Can Bettermode trigger a FlowRunner workflow automatically?

Bettermode doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Bettermode

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us