Skip to content
AI Marketplaces Leaderboard

Bland

ChatGPT plugin

Manage voice agents and calls

View in ChatGPT directory

Build and operate Bland v2 voice agents from ChatGPT. Design agent scenarios, review or update saved configurations, inspect environments and release checks, test behavior, and manage authorized deployments.

Analyze calls and conversation cohorts, work with evaluation judges and dispositions, connect knowledge sources and tools, and manage agent channels, existing phone numbers, outbound calls, automations, and triage issues where the connected tools support them. Includes detailed v2 product references and a named endpoint index.

Requires a Bland account and access to the connected organization. Sign in through Bland. Tool availability and permissions determine which operations can run. Calls, tests, evaluations, and other usage can consume existing entitlements. Purchases are not supported. Local snapshot validation and migration helpers require a host with workspace files and Node.js; unavailable execution or integration steps are reported explicitly.

Featured
No

not on the featured shelf

Movement

From our daily snapshots over the last 30 days.

Rank by placement

#5748of 8,79341places up24h90places up7d
#5,677#5,893#6,109#6,325Sep 27Oct 3Oct 9Oct 15Oct 21Oct 26

Rank in Developer tools

#519of 7422places up24h5places up7d
#516#526#536#546Sep 27Oct 3Oct 9Oct 15Oct 21Oct 26

3 listing changes logged · latest Oct 24: Description, Skills, Version. See what changed

In its category

How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.

Developer tools519th of 742 by placement
#PluginPosition7d
517invinoveritas#570825places up
518TokenOS Tokenomics Designer#573299places down
519BlandThis page#574890places up
520TokenOS Gas Tracker#5761105places down
521Uptimely#578278places down

All 742 Developer tools plugins

Example prompts

  • “List my Bland agents.”
  • “How many Bland calls completed last week?”
  • “Help me review a Bland call's transcript and outcome.”

Skills

  • agent-channels

    Use when someone wants to "embed chat on my site" or set up a "web chat widget", use the "chat API" or "turn on API chat", "text my customers", "reply to this thread", "take over this conversation" or hand it back, set up "WhatsApp", "A2P", "branded caller ID" or an "RCS contact card", or asks "why isn't the agent answering texts" or "which version answers texts", on Channels (Web chat, API chat, Messages), Identity or the Conversations page.

  • agent-environments

    Use when working on an agent's Environments or Variables page ("set an env variable", "add {{env.KEY}} for production", "AGENT_VARIABLE_UNRESOLVED", "set up checks before promote", "why is promote blocked", "test my branch", "merge the branch", "the branch is behind"), covering the unresolved-variable pre-flight, the staging check policy and verdicts, and branch, rebase and merge.

  • agent-launch

    Use when someone wants to take a v2 agent from built to live end to end ("launch my agent", "go live", "set it up so it answers calls", "put it in production", "what's left before launch", "onboarding checklist"), including getting a number, teaching it from documents, wiring tools, picking a voice, testing, promoting and turning on chat or texting. Each step hands to its own skill; this skill owns the order and the checklist.

  • analytics

    Query Bland call volume, completion rates, and other aggregate metrics over a specified period using the named analytics tool.

  • analytics-authoring

    Use when building, editing, simplifying or explaining an agent's analytics Sankey ("Where conversations go"): waypoint stages and groups, parallel branches, the unclassified share, what the Simplified and Detailed views draw, or why an end state cannot be split. Covers the customer waypoint-definition API (read, validate, save pending, preview, publish), its caps, and the boundary with dispositions.

  • analytics-cohorts

    Use when building a list or cohort of conversations that match a condition ("show me the calls where…", "which calls…", "how many calls…"), counting calls by lake columns, filtering by outcome, call length, metadata, tools, webhooks or disposition values, opening a filtered list on the Conversations page, feeding a set of calls to a judge run, reading, adding, editing, deleting or backfilling a headline metric tile on the Analytics page ("add a metric", "what's my containment", "how is the agent doing", also from an Overview page), or explaining why a condition cannot be expressed.

  • api-workspace

    Use when working with the Bland API from a coding workspace, finding product documentation, using named endpoint tools because bland_api_get or call_bland_api is unavailable, editing agent JSON instead of clicking the dashboard, reconciling unsaved page context with saved versions, or debugging a failed Bland operation. Covers API discovery, workspace evidence, and page synchronization; not v1 pathway authoring.

  • automations

    Use when someone says "when a call ends, do X", "when a CRM record changes, call them", "set up a trigger", "test my automation", "how do automations work", "why didn't my automation fire", "pause the automation", "alert me when", "resend the webhook" or asks about the "post-call webhook", on the Triggers or Alerts pages or an agent's Automations or Alerts tab.

  • call-analysis

    Use when finding, reviewing, categorizing, or analyzing Bland calls or conversations in bulk ("show me this agent's calls", "read the texts", "web chat threads", "export the calls"), including hundreds or thousands of recent calls, an agent's SMS, iMessage, WhatsApp, RCS, API chat or web chat threads, reproducing a specific call failure (tool logs, knowledge retrievals, SIP ladder, call scores), or producing a reproducible workspace report with evidence; also for calls in progress ("who is on a call right now", "end this live call", "transfer this call", "can you listen in") and contacts ("everything about this caller", "merge these contacts", "why is this caller not a contact") on the Active calls and Contacts tabs. Covers paginated API retrieval, agent scoping, server export, and code-based analysis without putting full datasets in chat.

  • dispositions

    Use when working on an agent's Dispositions page or post-call outputs ("set up dispositions", "track call outcomes", "extract fields after each call", "classify every call", "send the outcome to my webhook", "why is this disposition blank", "the disposition is wrong", "it didn't run", "backfill", "score past calls", "roll back the disposition", "migrate my citations"), covering definitions, extractors, test runs, corrections and align, estimates and publish, rollback, backfills and moving v1 citations and outcomes.

  • docs

    Find and explain official Bland product documentation, including features that the ChatGPT plugin cannot execute, using the named documentation search and retrieval tools.

  • evaluations

    Use when creating or calibrating Bland evaluation judges ("align this judge", "correct this verdict"), configuring test cases and attached judges, building judge workbench panels, running or interpreting evaluations and simulations, applying verdicts as call tags, or investigating failed, partial, or inconclusive scores. Distinguishes voice agents, evaluation judges, test scenarios, saved call cohorts, and asynchronous run results.

Show all 26
  • knowledge-sources

    Use when someone wants to "teach the agent", "add this doc / FAQ / website / file", says "the agent doesn't know", asks "what couldn't it answer", "what is it weakest on" or "what did it look up on this call", wants to "answer these questions", "test this source", "update the source", "re-sync" or "delete this source", asks how knowledge works, on the Knowledge pages (Sources, Questions, Query logs, Source testing, Knowledge map).

  • outbound-calls

    Use when placing or scheduling outbound calls with a v2 agent ("call this number with my agent", "place a call", "schedule a call"), running a campaign ("run a campaign", "call this list", "batch"), stopping one ("stop the batch"), or checking recipients ("is this number on the DNC"), including from the Send call and Batches pages.

  • pathways

    Inspect or validate a user-supplied native Bland pathway graph with the pathway schema, context, and compiler tools. Requires nodes and edges, not just a pathway ID.

  • phone-numbers

    Use when someone asks "who answers this number", wants to "put my agent on a number" or "point +1… at" an agent, "buy a number", "block this caller", a "fallback number" or transfer on a number, a "SIP trunk", or asks "why is my number not answering", on the Phone numbers page, the SIP pages, or an agent's Calls channel. Also DNC, and hand-offs for release, port-in and Twilio import.

  • setup

    Connect Bland to ChatGPT with OAuth, verify the connection, or troubleshoot sign-in, organization access, and authorization errors.

  • tool-library

    Use when someone wants to "create a tool", "call my API from the agent", "wire up a webhook", says "the tool returns HTTP 0" or "why did the tool fail on this call", asks "how do tools work" or "what does the caller hear while it runs", wants to "update the shared tool", "delete this tool" or asks "which agents use this tool", wants to "add a secret", "connect HubSpot / Salesforce" or "disconnect" an integration, or wants "custom code" in a tool, on the Tools, Secrets or Connections pages.

  • triage-issues

    Use when filing or working issues on the Issues page, org-wide or for one agent ("file an issue", "log this bug", "track this", "this call went wrong, record it", "attach this call to the issue", "close the issue", "link these issues", "what's open on this agent", "flag a capability gap"), including evidence, flags, assignment, alert bindings and billed eval analysis.

  • v2-authoring

    Designing and building a NEW Bland v2 agent from scratch — scenario architecture (what scenarios represent and where boundaries belong), hub + entry authoring, step/edge/tool design, the standard conduct-rule set, and how v2 building differs from v1 pathway building. Use when creating a new v2 agent, designing its scenarios, or when someone asks how building in v2 differs from v1. If the user has not said v1 or v2, ASK before applying this doctrine.

  • v2-lifecycle

    Use when shipping a Bland v2 agent version to real traffic or asking which version answers ("publish to staging", "promote to production", "roll back", "which version is this call running", "my fix didn't take"), running an A/B test or staged rollout on the Experiments page ("start an experiment", "ramp the new version", "finish the rollout", "pick the winner"), attaching inbound numbers, deleting an agent, setting an agent's voice and language ("change my agent's voice", "make it speak Spanish"), or on the Pathways page ("copy this pathway to another agent", "update the pathway in all my agents", "pathway versions").

  • v2-maintenance

    Use when updating, repairing, debugging, or managing an existing Bland v2 agent, including prompt edits, routing, tools, settings, versions, environment configuration, and regression testing.

  • v2-migration

    The hand-migration doctrine for converting a Bland v1 pathway or persona (raw JSON export) into a v2 agent snapshot — architecture rules, verbatim-carriage discipline, the full trap catalog, and the verification bar. Use whenever migrating or converting v1 pathways/personas to v2 agents, or when a migrated agent misbehaves. The /norm:migrate command drives this skill end to end.

  • v2-runtime

    Use when predicting or debugging Bland v2 runtime behavior, explaining routing or interruptions, explaining which version or runtime answered a call, web chat, API chat or text, explaining how an attached or library tool runs, or reconciling edited snapshot JSON with the builder canvas, hidden routes, and call traces.

  • v2-snapshot

    The Bland v2 agent snapshot dialect, the exact JSON shape of an agent version (behavior graph, hub, complex scenarios, flow steps, edges, tools, settings) and the rules for authoring one by hand. Use whenever reading, writing, or debugging an agent_versions snapshot, pushing a version via POST /v2/agents/:id/versions, or carrying content into a snapshot during migration.

  • v2-testing

    Use when verifying Bland v2 agents with simulations, test chat, or speech-to-speech tests; testing a text or messaging reply ("preview the SMS reply", "test the API chat"); placing a real test call to the agent's number; measuring interruptions or response latency; grading engine traces; or deciding whether a test is safe. Covers fixtures, the agent-testing API, messaging probes, voice evidence, and live-integration safety.

Categories
Made by
Bland · Website
Sign-in
On Install
Capabilities
Read, Write
Availability
Available
Version
2.3.0
Keywords
bland, voice-ai, voice-agents, conversational-ai, calls, pathways, analytics, mcp
Created
October 2, 2026
More info
Sponsorship
Promote this plugin