ChatGPT Plugin

Channlworks

Alliance Intelligence Platform

Brand: Channlworks

Category: Sales & CRM
Primary Subcategory: Partner & Ecosystem Revenue

Integration details

Description

Connect to Channlworks to find and summarize partner relationships, customer accounts, contacts, deals, campaigns, MDF requests, receivables and payables claims, notes, and programs. Create or update supported records and carry out supported approval workflows when your Channlworks role permits them. Access is scoped to the signed-in user and active organization. Sign in to a Channlworks organization with MCP Access enabled.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Sales & CRM
Primary Subcategory: Partner & Ecosystem Revenue
Secondary Subcategories: None listed
Brand: Channlworks
Access: Account required
First tracked: 2026-10-27
Tool count: 73
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 Partner & Ecosystem Revenue

View Category

Listed in alphabetical order

Primary Subcategory

ChannlworksComing soonGet notified

CrossbeamComing soonGet notified

EULERComing soonGet notified

Introw PRMComing soonGet notified

LuasaiComing soonGet notified

Tools

73 tools agents can invoke

Adds exceptional approvers to a campaign, so people beyond the configured approver can approve it. Approvers already listed are skipped, and newly added approvers are notified. When the campaign is pending approval each new approver also receives a pending approval request; in any other status they are only recorded on the campaign.
add_campaign_exceptional_approvers
Adds approvers to a deal that is pending approval so more people must sign off before it can proceed. Requires approval-management rights. Approvers already assigned to the deal are ignored; the notification to the new approvers cannot be recalled.
add_deal_additional_approvers
Approves a campaign that is pending approval, optionally recording an approval reason and adding exceptional approvers. The campaign owner, creator and approver are notified.
approve_campaign
Approves a deal that is pending approval, either by resolving the caller's own pending approver request or, for users with approval-management rights, by resolving all pending requests at once. Only a submitted deal that is currently pending can be approved, and a deal already approved cannot be approved a second time — an edited submitted deal re-enters approval on its own.
approve_deal
Links several deals to an ACTIVE campaign in one request, each with its own attribution type and evidence note. The same deal and attribution type cannot appear twice in one request, and SOURCED attribution requires a deal sourced from Campaigns plus a non-empty evidence note. The campaign's creator, owner and approver are notified.
bulk_link_campaign_deals
Cancels an ACTIVE campaign, optionally recording a reason. The campaign is kept with its history rather than deleted, and its participants are notified.
cancel_campaign
Writes a campaign's status directly to any of DRAFT, PENDING_APPROVAL, ACTIVE, COMPLETED or CANCELLED, for vendor admins only. This is a direct administrative write: no approval step runs, no status transition is rejected as invalid, and nobody is notified. The dedicated submit, approve, reject, complete, cancel and reactivate operations run those workflow checks and do notify campaign participants.
change_campaign_status
Marks an ACTIVE campaign complete, optionally recording a reason. A campaign that requires approval can only be completed by a vendor admin. Deals stay linked and keep their attribution, and the campaign participants are notified.
complete_campaign
Closes a deal's Proof of Value, recording whether the evaluation succeeded and optional outcome notes, and optionally attaching up to five evidence files. Requires an existing POV that has not been completed; completion is final and cannot be repeated.
complete_deal_pov
Creates an ARAP claim (submitted) with a category, currency, claimed amount, primary approver, and at least one PAYER partner map. Optional: collaborators, linked sources, and documents based on claim category requirements.
create_arap_claim
Creates a campaign with name, type, dates, budget, owner, sharing settings and an optional approver. The status may be DRAFT, PENDING_APPROVAL or ACTIVE, so a campaign can be created straight into an active state without a separate submission step. Participants and the approver are notified, which cannot be recalled, and the campaign joins the shared campaign list of any partner it is shared with.
create_campaign
Creates a customer (end-customer) contact with name and email, plus optional account association, address, company, role, visibility, and phone numbers. The contact type is always CUSTOMER — vendor and partner contacts come from the partner's own organization record. Creating a contact records a contact event, notifies the people involved, and enqueues an outbound CRM sync, so the side effects cannot be recalled afterwards.
create_customer_contact
Creates a customer (end-customer) account with name and domain, plus optional address, industry, owner, size and phone numbers. Only CUSTOMER accounts can be created here — vendor and partner organizations are created through organization management. Creation notifies the account stakeholders and enqueues an outbound CRM sync, so the side effects cannot be recalled afterwards.
create_account
Creates a deal with optional partner mappings, product selections, customer account and contact association, tags, and approval workflow configuration. A submitted (non-draft) deal starts the approval workflow, notifies the approver and anyone copied on the deal, and enqueues an outbound CRM sync; a draft deal records the deal without notifying anyone and can be submitted later with update_deal. Proof of Value is not configured here — request_deal_pov creates it on a deal that has none.
create_deal
Creates a Market Development Fund (MDF) request for the caller's organization, with a purpose and amount, optional event details, dates, and an approval workflow configuration. Fields are conditional on purpose: non-cash purposes require purposeValue NON-CASH and a code, cash purposes require a percentage, and event purposes require eventName and expectedOutcomes. A submitted request notifies its approver and collaborators, which cannot be recalled; a draft request can be submitted later.
create_mdf_request
Creates a note on a deal, MDF request, or account, attributed to the caller. Participants named on the note are emailed, which cannot be recalled.
create_channl_note
Adds a comment by the caller to an existing note and emails the note's participants, which cannot be recalled.
create_channl_note_comment
Creates a partner program with configurable tiers. Each tier defines requirements (revenue targets, certifications, location coverage, etc.) and benefits (margin settings, MDF allocations). A new program starts in DRAFT status and accepts no enrollments until its status is set to ACTIVE; creating it notifies nobody.
create_program
Permanently deletes a deal and its partner mappings, tags and POV records. Requires deal management rights. Deals that carry a renewal reminder or are submitted renewals cannot be deleted.
delete_deal
Enrolls the caller's partner organization in an ACTIVE program, creating the enrollment record and starting compliance tracking against the program's tiers. Available to partner users for vendor-run programs; only a program in ACTIVE status accepts enrollments, and an organization cannot enroll in a program it created itself.
enroll_in_program
Fetches full details for a single ARAP claim by its UUID, including category, requirements, documents, partner maps, and linked sources.
get_arap_claim
Returns a campaign's approval history, including each approver's status and resolution. Read-only.
get_campaign_approval_history
Returns a cross-campaign summary across the caller's visible campaigns: total counts, sourced and influenced pipeline, won revenue, and status and type distributions. Read-only.
get_campaign_dashboard_summary
Returns the deals linked to a campaign. Read-only. Partners see only the deals their own organization linked; vendor admins see every linked deal.
get_campaign_deals
Returns one campaign in full: status and approval state, dates, budget and currency, creator, owner, approver, collaborators, expected outcomes, shared partners, connected deal count, and sourced/influenced pipeline with won revenue. Read-only.
get_campaign_details
Returns a campaign's audit timeline: created, approved, rejected, completed, cancelled, reactivated and deal link/unlink events with their actors and timestamps. Read-only.
get_campaign_logs
Returns the MDF request totals for a campaign — amount requested and amount approved. Read-only.
get_campaign_mdf_summary
Returns a campaign's aggregated metrics: pipeline, revenue and deal counts broken down by attribution type. Read-only.
get_campaign_metrics
Returns the partner maps (tenant relationships) a campaign is shared with. Read-only.
get_campaign_partner_maps
Returns a paginated list of campaigns with optional filtering by status, type, and search term. Read-only; visibility respects RBAC and partner sharing rules.
get_campaigns
Returns a paginated list of customer (end-customer) accounts, filterable by search text or a single account ID, and sortable. Read-only. Partner organizations are a separate population, listed by get_all_ecosystem_accounts.
get_all_customer_accounts
Returns a paginated list of customer contacts — contacts recorded at end-customer accounts — with free-text search and sorting. Read-only. Partner-side contacts are a separate population, listed by get_all_ecosystem_contacts.
get_all_customer_contacts
Returns full detail for one deal: its fields, partner mappings, accounts, contacts, products, tags, approval statuses and Proof of Value state. Read-only.
get_deal_by_id
Returns a deal's activity timeline, newest first: created, updated, submitted, approved, rejected, POV and renewal events. Read-only.
get_deal_logs
Returns a deal's approval history: each approver request with its sequence, status and resolution. Read-only.
get_deal_approval_history
Returns the active product SKUs the caller may attach to a deal, each with catalog metadata, list price and minimum order quantity. Read-only. Typical use is to resolve the productSkuId values that create_deal and update_deal accept.
get_deal_product_options
Returns a paginated list of deals visible to the caller, with optional filters on stage, approval status, tags and draft state, plus free-text search. Read-only; visibility follows the caller's partner mappings and role.
get_deals
Returns a paginated list of ecosystem accounts — the partner organizations the caller works with — filterable by search text or a single account ID, and sortable. Read-only. Customer accounts are a separate population, listed by get_all_customer_accounts.
get_all_ecosystem_accounts
Returns a paginated list of ecosystem contacts — contacts belonging to the partner organizations the caller works with — with free-text search and sorting. Read-only. Customer contacts at end-customer accounts are a separate population, listed by get_all_customer_contacts.
get_all_ecosystem_contacts
Returns the partner relationships the caller's organization has established: each partner organization with the relationship's identifiers and status. Read-only. These are existing relationships inside the caller's ecosystem; search_public_partners looks up companies in a public directory that the caller has no relationship with.
get_ecosystem_relations
Returns the contacts linked to the given partner map IDs as names, email addresses, tenant IDs, user-view labels, and approver flags. Omitting partnerMapIds returns the contacts already visible in the caller's active organization. Read-only. This read is scoped by partner relationship; get_all_ecosystem_contacts and get_all_customer_contacts are the paginated, searchable listings of the same contact population.
linked_vp_contacts
Returns a paginated list of Market Development Fund (MDF) requests visible to the caller, filterable by approval status, vendor, partner, state, purpose and MDF ID, with search and sorting. Read-only.
get_mdf_requests
Returns the notes attached to one record, newest first. moduleType selects the record family the notes hang off: Deals, MDF, or Accounts, and moduleRefId is that record's ID. Read-only. Comments on an individual note are listed by get_channl_note_comments_by_note_id.
get_channl_notes_by_module_id
Returns one note with its header, content, author, participant list and note date. Read-only. The comments on the note are listed by get_channl_note_comments_by_note_id.
get_channl_note_by_note_id
Returns every comment on one note, in the order they were added. Read-only.
get_channl_note_comments_by_note_id
Returns the partner organizations enrolled in a program with each partner's ID and name, assigned tier ID and name, and tier display color. Read-only.
get_all_partners_compliance
Returns one program with its tiers, requirements, benefits, and the caller's own enrollment status where applicable. Read-only.
get_program_details
Returns the organizations available to the authenticated user, each with the user's role and login type for it. With no type it lists the organizations the user is already a member of; JOINABLE_TENANTS lists organizations the user can join, and CONNECTED_TENANTS lists the user's connected organizations. These are the user's own organizations, not partner organizations — partner organizations are listed by get_all_ecosystem_accounts. Read-only.
get_tenants
Returns the authenticated user's session record: name, email, phone, role, admin flag, membership status, login type, onboarding flags, the active organization with its partner map IDs, and every organization the user belongs to with the per-organization role. Pass activeTenantId to scope the session to one organization the user belongs to; omitting it uses the caller's currently active organization. Read-only.
get_user_details
Returns the authenticated user's identity-provider profile: display name, username, avatar image URL, email addresses, and account created/updated/last-sign-in timestamps. Read-only. This is the profile record itself, which carries fields the session record from get_user_details does not (username, avatar, per-address emails, sign-in history), while roles, organizations and admin status live on that session record.
get_user_identity_profile

FAQs

Channlworks ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Channlworks'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 Channlworks alternatives on ChatGPT?

As of 2026-10-28, Channlworks competes with Crossbeam, EULER, Introw PRM, Luasai, Nesha, Partner.io, Suger in ChatGPT Partner & Ecosystem Revenue, 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.