ChatGPT Plugin

Canny

Capture and analyze feedback

Brand: Canny

Category: Data & Analytics
Primary Subcategory: Customer Feedback & Research Platforms

Integration details

Description

Canny’s app connects ChatGPT to your customer feedback data. Use it to uncover insights, take action, and stay organized. Ask questions about your feedback: - What are my top feature requests by ARR? - What are enterprise customers asking for most? - What did the product team ship last quarter? Capture and triage feedback: - Send a call transcript or support ticket and Autopilot will capture, deduplicate, and triage feedback automatically - Attribute feedback to a specific user and/or company - Link Salesforce opportunities or HubSpot deals to ideas Manage your roadmap: - Ensure feedback is organized so teams can access their feedback - Create and update views to look at focused lists of feedback - Update statuses and other custom fields to keep your team and customers in the loop

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Data & Analytics
Primary Subcategory: Customer Feedback & Research Platforms
Secondary Subcategories: None listed
Brand: Canny
Access: Account required
First tracked: 2026-07-21
Tool count: 63
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Customer Feedback & Research Platforms

View Category

Listed in alphabetical order

Primary Subcategory

AppbotComing soonGet notified

AppReviewBotComing soonGet notified

CannyComing soonGet notified

CentralizaComing soonGet notified

ClootrackComing soonGet notified

Tools

63 tools agents can invoke

Adds an association between the given user and company.
add_user_to_company
Creates a new changelog entry, optionally publishing it immediately or scheduling it for later. Entries are created as drafts unless `published` or `scheduledFor` is provided.
create_changelog_entry
Creates a new company. Recurring revenue is optional, but `spend` and `spendType` (`mrr` for monthly recurring revenue, `arr` for annual recurring revenue) are all-or-nothing: provide both or neither. When asking a user for revenue, use the SaaS terms — e.g. "What's this company's ARR?". If the user gives a figure without saying whether it's MRR or ARR, ask before creating the company.
create_company
Creates a new group used to organize ideas.
create_group
Creates a new idea. Use this tool to collect feedback from the user. Pass `insight` with a `companyID` and/or `userIDs` to attribute the idea to the customer who asked for it: that records an insight on the new idea, returned as `insight`. By default, user-related identifiers in the returned idea are omitted. Pass `include: ["users"]` to include user-related identifiers.
create_idea
Creates an idea comment on the idea's activity tab, authored by the connected user. Idea comments are visible only to admins, never appear on the portal, and do not change the idea's status or notify voters, so use them for internal progress notes. To post on the portal, use `create_portal_comment` instead. Pass `mentionedAdminIDs` to notify admins; they are appended to the comment as a "cc" line. Pass `parentID` to reply to an existing root-level idea comment. By default, user-related identifiers in the returned comment are omitted. Pass `include: ["users"]` to include them.
create_comment
Creates a new insight on an idea, capturing feedback from a customer (an end user, a company, or both). At least one of `companyID` or `userIDs` must be provided. When both are provided and the user is not already associated with the company, an association will be created. By default, user-related identifiers in the returned insight are omitted. Pass `include: ["users"]` to include them.
create_insight
Creates a portal comment for a specific idea, authored by the connected user. The idea must be published to the portal. Portal comments live on the portal and are distinct from idea comments (`list_comments`). Pass `parentID` to reply to an existing root-level comment. By default, user-related identifiers in the returned comment are omitted. Pass `include: ["users"]` to include them.
create_portal_comment
Creates a new user segment used for user segmentation. The segment is defined by a name and a list of attribute filters. Use the list_segment_fields and list_segment_operations tools first to discover valid field IDs and operators.
create_segment
Creates a new end-user in the company and returns its ID and admin URL. Providing an `email` is strongly recommended: it helps deduplicate against existing users (if one already has that email, it is returned instead of creating a duplicate).
create_user
Creates a new View.
create_view
Deletes a changelog entry.
delete_changelog_entry
Deletes a group, its sub-groups, and views scoped to those groups. Ideas in those groups are kept and ungrouped by default; pass `moveIdeasToGroupID` to move them to another group instead. Set `preserveIdeas` to false to delete the contained ideas too. Use `list_groups` to find valid group IDs.
delete_group
Deletes an idea. The idea, along with all of its descendants, insights, and related data will be deleted. Use the `list_ideas` tool to discover valid idea IDs.
delete_idea
Deletes an insight.
delete_insight
Deletes a portal comment and its replies. Discover valid IDs via the `list_portal_comments` tool. These are portal comments, distinct from the idea comments managed by the `list_comments` and `create_comment` tools.
delete_portal_comment
Deletes a view. Default views and the last remaining view in a group cannot be deleted.
delete_view
Links a Salesforce opportunity or HubSpot deal to an idea. Provide exactly one of `salesforceOpportunityID` or `hubspotDealID`. To also capture customer feedback, call the `create_insight` tool separately.
link_opportunity
Read-only: Returns all admin teammates, including each admin name so callers can identify users. By default, admin IDs are omitted. To include IDs for use with other tools that accept admin IDs, pass `include: ["ids"]`. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_admins
Read-only: Returns categories that belong to the provided board. Categories may be nested via `parentID`.
list_board_categories
Read-only: Returns tags that belong to the provided board sorted by newest first.
list_board_tags
Read-only: Returns all boards. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_boards
Read-only: Returns changelog entries, filtered and sorted by the given parameters.
list_changelog_entries
Read-only: Returns all changelog labels. Labels are used to categorize changelog entries.
list_changelog_labels
Read-only: Returns a list of all companies associated with your company, ordered by created date, optionally filtered by search query or scoped to a segment.
list_companies
Read-only: Returns all groups used to organize ideas. Groups are organizational units that group ideas together. Each idea belongs to one or no group. Groups can be nested to create a hierarchy of groups. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_groups
Read-only: Returns idea comments from a specific idea's activity tab. Use `create_comment` to add one. Mentions in comment text are converted to readable plaintext names. By default, user-related identifiers are omitted. Pass `include: ["users"]` to include them.
list_comments
Read-only: Returns all fields that can be used when filtering ideas, including default fields and company-specific custom, score, and formula fields. Each field includes its ID, type, label, whether it has predefined options, and whether it is a default or custom field. For default fields with predefined options, use `list_groups` for the `group` field, `list_idea_statuses` for the `status` field, and `list_idea_themes` for the `themes` field to discover valid option IDs. Use this together with `list_idea_filtering_operations` when constructing the `filtering` parameter for `list_ideas`. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_idea_fields
Read-only: Returns all the filtering options that can be used in idea filters, including the input type they expect and which idea field types they apply to. Use this together with `list_idea_fields` to construct valid `filtering.filters` entries for the `list_ideas` tool. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_idea_filtering_operations
Read-only: Returns a paginated list of insights linked to a specific idea, including priority, source, the company each is attributed to, and linked comment/vote IDs. By default, user-related identifiers are omitted — pass `include: ["users"]` to include them.
list_insights
Read-only: Returns a paginated list of opportunities linked to an idea. An opportunity represents a potential customer, synced in from Salesforce or Hubspot. Opportunities linked to descendant ideas are included and deduplicated. To link or unlink opportunities, use the `link_opportunity` and `unlink_opportunity` tools respectively.
list_idea_opportunities
Read-only: Returns all idea statuses. Use this to filter ideas by status when calling the `list_ideas` tool. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_idea_statuses
Read-only: Returns all idea themes. Themes are used to categorize ideas into more general topics. Each idea can be assigned to one or no theme. Use these to filter ideas by theme when calling the `list_ideas` tool. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_idea_themes
Read-only: Returns a list of ideas, filtered and sorted by the given parameters. Use the `list_idea_fields` and `list_idea_filtering_operations` tools to discover which fields you can filter and sort by using this tool. By default, user-related identifiers are omitted, and user-typed fields (default and custom) are excluded from `fields`. Pass `include: ["users"]` to include user-related identifiers and user-typed fields. Pass `segmentID` to scope segmentable metrics to a company segment. Note this tool lists *Canny Ideas*, not to be confused with *Canny Posts*. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations. If you already know the idea ID or urlName (for example, parsed from a Canny URL), prefer the `retrieve_idea` tool — it is faster and more accurate than searching with this tool.
list_ideas
Read-only: Returns a paginated list of comments left on the portal. By default, it returns portal comments across all published ideas in the company. Mentions in comment text are converted to readable plaintext names. By default, user-related identifiers are omitted. Pass `include: ["users"]` to include them. These are portal comments, distinct from the idea comments managed by the `list_comments` and `create_comment` tools.
list_portal_comments
Read-only: Returns all portal statuses (the public-facing statuses shown on the portal/roadmap). Use this to discover valid status IDs and names before changing a status or filtering by one.
list_portal_statuses
Read-only: Returns the end-users who voted on a specific idea, each with the vote's priority, the voter's company, and when they voted. By default, user identifiers and emails are omitted — pass `include: ["emails"]` for each voter's email and `include: ["ids"]` for their user ID.
list_portal_voters
Read-only: Returns all fields that can be used to define user segments, including both standard and custom fields. Each field includes its ID, source (`standard` or `custom`), fieldType (`boolean`, `number`, `date`, or `string`), objectType (`company` or `user`), and human-readable name. Use this before creating or updating segments to understand available attributes. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_segment_fields
Read-only: Returns all operations that can be applied to segment attributes, with a short human-readable description of each. Use this to understand how to define attribute filters when creating or editing segments. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_segment_operations
Read-only: Returns all user segments, ordered by name. Use this to understand how users are segmented. Attribute `id`s are field identifiers: use the `list_segment_fields` tool to resolve them to human-readable fields and `list_segment_operations` to interpret each `op`. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_segments
Read-only: Returns end-users in this workspace, optionally filtered by name or email. To fetch a specific set of users by their IDs, use `retrieve_users` instead.
list_users
Read-only: Returns saved idea views, including their filters, grouping, and sort configuration. Use this to discover view IDs and settings you can reference when calling the `list_ideas` tool (for example via the `viewID` parameter) or when constructing custom filters. This tool is not idempotent: underlying data can change between calls, so avoid relying on cached results during longer conversations.
list_views
Merges two ideas together. The source idea (fromIdeaID) will be merged into the target idea (intoIdeaID). All descendants, insights, and related data from the source idea will be moved to the target idea, and the source idea will be marked as deleted. Use the `list_ideas` tool to discover valid idea IDs.
merge_ideas
Moves an idea to a different group and/or reparents it under another idea. At least one of `groupID` or `parentID` must be provided. A sub-idea must belong to the same group as its parent.
move_idea
Moves an insight to a different idea. Insights linked to a vote, or to a comment someone wrote on the portal, cannot be moved.
move_insight
Removes a user's membership from the given company.
remove_user_from_company
Read-only: Returns a single company looked up by its ID.
retrieve_company
Read-only: Returns a single group looked up by its ID or its urlName. Groups are organizational units that group ideas together. Exactly one of `id` or `urlName` must be provided. Discover valid IDs via the `list_groups` tool.
retrieve_group
Read-only: Returns a single idea looked up by its ID or by a link to it. Exactly one of `id` or `url` must be provided.
retrieve_idea
Read-only: Returns a single end-user looked up by `id` or `email`.
retrieve_user

FAQs

Canny ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Canny's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Canny alternatives on ChatGPT?

As of 2026-11-02, Canny competes with Appbot, AppReviewBot, Centraliza, Clootrack, Conveo, countrymanager, Dovetail, empirio.ai and 34 more in ChatGPT Customer Feedback & Research Platforms, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.