Appcues connector for AI agents

Tools your growth agent reaches for on Appcues, scoped per user.

CALL ANY TOOL

API Key product experiences tools: flows, pins, NPS, segments, users, and publish controls on Appcues.

appcues_add_users_to_group

Add Users To Group

Add a list of end users to a group by user ID.

Parameters

Name

Type

Required

Description

group_id

string

Required

The Group ID.

user_ids

array

Required

List of end user IDs to add to the group.

appcues_add_users_to_segment

Add Users To Segment

appcues_create_sdk_key

Create Sdk Key

appcues_create_segment

Create Segment

appcues_create_user_event

Create User Event

appcues_delete_sdk_key

Delete Sdk Key

appcues_delete_segment

Delete Segment

appcues_delete_user_profile

Delete User Profile

appcues_disable_enforcement_mode

Disable Enforcement Mode

appcues_disable_secure_data_ingest

Disable Secure Data Ingest

appcues_enable_enforcement_mode

Enable Enforcement Mode

appcues_enable_secure_data_ingest

Enable Secure Data Ingest

appcues_export_events

Export Events

appcues_export_segment_membership

Export Segment Membership

appcues_get_banner

Get Banner

appcues_get_checklist

Get Checklist

appcues_get_embed

Get Embed

appcues_get_filtering_rules

Get Filtering Rules

appcues_get_flow

Get Flow

appcues_get_flow_v2

Get Flow V2

appcues_get_group_profile

Get Group Profile

appcues_get_job

Get Job

appcues_get_launchpad

Get Launchpad

appcues_get_mobile_experience

Get Mobile Experience

appcues_get_nps

Get Nps

appcues_get_pin

Get Pin

appcues_get_screenshots

Get Screenshots

appcues_get_segment

Get Segment

appcues_get_tag

Get Tag

appcues_get_user_profile

Get User Profile

appcues_list_banners

List Banners

appcues_list_checklists

List Checklists

appcues_list_embeds

List Embeds

appcues_list_flows

List Flows

appcues_list_flows_v2

List Flows V2

appcues_list_jobs

List Jobs

appcues_list_launchpads

List Launchpads

appcues_list_mobile_experiences

List Mobile Experiences

appcues_list_nps_surveys

List Nps Surveys

appcues_list_pins

List Pins

appcues_list_sdk_keys

List Sdk Keys

appcues_list_segments

List Segments

appcues_list_tags

List Tags

appcues_list_user_events

List User Events

appcues_publish_banner

Publish Banner

appcues_publish_checklist

Publish Checklist

appcues_publish_embed

Publish Embed

appcues_publish_flow

Publish Flow

appcues_publish_flow_v2

Publish Flow V2

appcues_publish_launchpad

Publish Launchpad

appcues_publish_mobile_experience

Publish Mobile Experience

appcues_publish_nps

Publish Nps

appcues_publish_pin

Publish Pin

appcues_remove_users_from_segment

Remove Users From Segment

appcues_unpublish_banner

Unpublish Banner

appcues_unpublish_checklist

Unpublish Checklist

appcues_unpublish_embed

Unpublish Embed

appcues_unpublish_flow

Unpublish Flow

appcues_unpublish_flow_v2

Unpublish Flow V2

appcues_unpublish_launchpad

Unpublish Launchpad

appcues_unpublish_mobile_experience

Unpublish Mobile Experience

appcues_unpublish_nps

Unpublish Nps

appcues_unpublish_pin

Unpublish Pin

appcues_update_group_profile

Update Group Profile

appcues_update_sdk_key

Update Sdk Key

appcues_update_segment

Update Segment

appcues_update_user_profile

Update User Profile

Build your Agent

Same auth pattern across every framework.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
const sk = new ScalekitClient();
const tools = await sk.tools.listScopedTools("user_123", { filter: { connectionNames: ["appcues"], toolNames: ["appcues_add_users_to_group", "appcues_add_users_to_segment", "appcues_create_sdk_key"] }, pageSize: 100 });
const agent = createReactAgent({ llm, tools });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient();
const tools = await sk.tools.listScopedTools("user_123", { filter: { connectionNames: ["appcues"], toolNames: ["appcues_add_users_to_group", "appcues_add_users_to_segment", "appcues_create_sdk_key"] }, pageSize: 100 });
const client = new OpenAI();

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient();
const tools = await sk.tools.listScopedTools("user_123", { filter: { connectionNames: ["appcues"], toolNames: ["appcues_add_users_to_group", "appcues_add_users_to_segment", "appcues_create_sdk_key"] }, pageSize: 100 });

import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient();
const tools = await sk.tools.listScopedTools("user_123", { filter: { connectionNames: ["appcues"], toolNames: ["appcues_add_users_to_group", "appcues_add_users_to_segment", "appcues_create_sdk_key"] }, pageSize: 100 });

Try these prompts

Paste any prompt into your agent to start on product experiences in Appcues.

Flows and experiences

Copy the prompt

Copied

List all published Flows and flag any draft that has not shipped in 30 days.

Copy the prompt

Copied

Open the Flow named Onboarding and summarize its steps.

Copy the prompt

Copied

Publish the checklist for new trial users after I confirm the copy.

Segments and users

Copy the prompt

Copied

List segments and show membership size for each.

Copy the prompt

Copied

Add these user ids to the power-users segment.

Copy the prompt

Copied

Export segment membership for churn-risk and email me the CSV.

NPS and pins

Copy the prompt

Copied

List NPS 2.0 surveys and show which are live.

Copy the prompt

Copied

Unpublish the pin on the billing page until the redesign ships.

Copy the prompt

Copied

Show the latest events for user_42 in the last 7 days.

SEE HOW AUTH WORKS

Your users connect once. Their Appcues API key and secret stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

Appcues

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Appcues

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Appcues

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Appcues

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Pair Appcues with analytics and CRM agents when product experiences need audience context.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A single Appcues bot key collapses every publish and segment change onto one service account. Scalekit resolves the signed-in user's key so audit rows name the real operator.

// shared key
audit → bot_acct

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Appcues today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Appcues as the user or a shared key?

Per-user. Scalekit stores each user's Appcues API key and secret and attaches them on every tool call so audit trails name the operator, not a shared bot.

Where is the Appcues token stored?

In Scalekit's AES-256 vault under a per-tenant namespace. Secrets are resolved at request time, never placed in LLM context, and can be revoked from one dashboard.

Can I limit what the agent does in Appcues?

Yes. Filter tool names in listScopedTools and Scalekit enforces those scopes before the Appcues API call, so publish tools can stay off a read-only agent.

What happens when a user revokes access?

The next tool call fails closed for that user. Other users keep their connections. The revoke is logged in the audit chain.

Can the agent publish Flows without a human check?

Only if you expose publish_* tools to that agent. Keep publish tools out of the scoped list when you want draft-only access; Scalekit will block the call before it hits Appcues.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit