ChatGPT Plugin

Assembly

Manage client work

Brand: Assembly

Category: Sales & CRM
Primary Subcategory: Customer Success Platforms

Integration details

Description

Assembly helps users work with clients from ChatGPT. Users can find clients and companies, manage tasks, notes, files, messages, forms, contracts, invoices, subscriptions, products, prices, app connections, notifications, and related workspace activity and records through authenticated Assembly APIs.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Sales & CRM
Primary Subcategory: Customer Success Platforms
Secondary Subcategories: None listed
Brand: Assembly
Access: Account required
First tracked: 2026-09-19
Tool count: 38
Market: US

AgentDiscoChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Not discoverable in ChatGPT yet

ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen Assembly suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.

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 Success Platforms

View Category

Listed in alphabetical order

Primary Subcategory

AssembledComing soonGet notified

AssemblyComing soonGet notified

EnclaveComing soonGet notified

Gainsight Customer CommunitiesComing soonGet notified

Velaris BasicComing soonGet notified

Velaris IntelligenceComing soonGet notified

Tools

38 tools agents can invoke

Build, check on and publish an app for the workspace with Assembly's App Builder. `create` starts a build from a prompt and returns the workspace's credit balance: tell the user what is being built and that it spends credits, and only create after they agree. The platform plans the app and then builds it; poll `status` for the plan, progress, `previewUrl` and any error. Use `turn` for a follow-up change and `publish` (only on request) to install the app into the workspace, then report the `deploymentUrl`. Only one build runs at a time; a `build_in_progress` reply means wait and poll `status`.
app_builder
Get reference information about the Assembly platform: product concepts, terminology (workspace, internal user, client user, company), and the feature/module map. Call this tool once per session for orientation when you need to understand what Assembly is or decide which feature a user's request maps to. For URL patterns used to link to dashboard views, call dashboard_links instead.
assembly_overview
Get the assistant's own identity for the authenticated user: its display name, the owner it belongs to, and its email address in each workspace. The identity is created on first use. Call this to answer questions like "what is your email address".
assistant_identity
Work with Clients. Clients are the external users your business serves through the portal. Actions: create, delete, list, retrieve, retrieve_app_visibility, update. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: companyId, givenName, familyName, email, customFields).
clients
Work with Companies. Companies group related client users together. Actions: add_clients, create, delete, list, retrieve, update. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: name, isPlaceholder).
companies
Work with Contract Templates. Contract templates are reusable blueprints for creating contracts. Actions: list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: name).
contract_templates
Work with Contracts. Contracts are signable documents sent to clients. Actions: create, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: status, contractTemplateId, recipientId, clientId, name).
contracts
Work with Custom Fields. Custom fields are user-defined data fields on clients and companies. Actions: create, delete, list, list_options, update. List defaults to limit=25; use filter params to narrow results (filterable by: name, entityType).
custom_fields
Get URL patterns and domain notes for constructing links into a workspace's Assembly dashboard (client details, company details, invoice details, message channels, etc.). Call this whenever a user asks you to link, share a URL, or send them to a specific dashboard view.
dashboard_links
Work with Events. Audit log events recording who did what and when in the workspace. Actions: create, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=50; use filter params to narrow results (filterable by: startDate, endDate, eventType, actorId).
events
Work with File Channels. File channels store documents shared with clients. Actions: create, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: companyId, clientId, membershipType, memberId, membershipEntityId).
file_channels
Work with Files. Files are documents uploaded and shared within channels. Actions: create, delete, download, download_url, list, retrieve, set_permissions. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: channelId, path). IMPORTANT — uploading a file is two steps: 'create' makes the record and returns a short-lived presigned Amazon S3 URL (the uploadUrl field) that the file bytes must then be separately PUT to ('download'/'download_url' likewise return S3 URLs to GET). That host looks like <bucket>.s3.amazonaws.com (an *.amazonaws.com host) and is blocked by default in sandboxed or network-restricted environments (e.g. Claude.ai), where the PUT is rejected with a 'host not allowed' error. Because the record is created before the bytes upload, a blocked upload leaves an unusable file stuck in 'pending' status. So in such an environment, have the user allowlist the S3 host (*.amazonaws.com) BEFORE creating files — or have them upload the file directly in the web app — and delete any leftover 'pending' file that never received its bytes with the 'delete' action.
files
Work with Files Root Permissions. Actions: replace
files_root_permissions
Request Form Responses. Form responses are submissions from clients for a specific form. Actions: create
form_responses
Work with Forms. Forms are intake forms that clients fill out. When creating a form, note that Assembly does not support conditional/branching logic — questions are presented as a flat, ordered sequence, so flatten any conditional questions when adapting a form from elsewhere. Actions: create, list, list_responses, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25.
forms
Work with Installs. Installs are marketplace apps added to the workspace. Actions: create_connection, create_notification_settings, list, list_connections, retrieve, retrieve_notification_settings, update_notification_settings. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: previewAsClient).
installs
Work with Internal Users. Internal users are team members who manage the workspace. Actions: list, retrieve, retrieve_notification_settings, update. For single lookups prefer 'retrieve' with an id. List defaults to limit=25.
internal_users
Work with Invoice Templates. Invoice templates are reusable blueprints for creating invoices. Actions: list. List defaults to limit=25.
invoice_templates
Work with Invoices. Invoices are payment requests sent to clients. Actions: create, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: clientId, companyId, includeCompanyInvoices, subscriptionId).
invoices
List all workspaces the authenticated user has access to. Use this to discover workspace IDs for multi-workspace accounts.
list_workspaces
Work with Me. Actions: list. List defaults to limit=25.
me
Work with Message Channels. Message channels are conversations between internal users and clients. Actions: create, list, retrieve, unread. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: clientId, membershipEntityId, companyId, memberId, membershipType, includeUnread).
message_channels
Work with Messages. Messages are individual chat messages within a message channel. Actions: create, list. List defaults to limit=25; use filter params to narrow results (filterable by: channelId).
messages
Work with Notes. Notes are internal-only records attached to clients or companies. Actions: create, delete, list, retrieve, update. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: entityId, entityType).
notes
Work with Notifications. Notifications are alerts about activity in the workspace. Actions: create, delete, list, mark_read, mark_unread, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: recipientId, recipientClientId, recipientInternalUserId, includeRead, recipientCompanyId).
notifications
Work with Payments. Payments track money received against invoices. Actions: list. List defaults to limit=25; use filter params to narrow results (filterable by: invoiceId).
payments
Work with Prices. Prices define the cost of a product for billing purposes. Actions: create, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: productId).
prices
Work with Products. Products are billable services offered to clients. Actions: create, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: name).
products
Search what the assistant remembers from this user's earlier conversations, on any channel. Use it when the user asks what was said or decided before ("what did we say about the Acme proposal"). query is the subject in plain words; since optionally limits results to conversations on or after a date (RFC 3339 or YYYY-MM-DD). Each passage carries its date, channel and thread so you can say when it was discussed and link back.
recall
Work with Refunds. Actions: create, list. List defaults to limit=25; use filter params to narrow results (filterable by: invoiceId).
refunds
Schedule a wake-up for the assistant, list the caller's schedules, or cancel one. action=create needs intent (the request in the user's own words) and exactly one of fireAt (RFC 3339 time) or cron (EventBridge cron body, e.g. "0 9 ? * MON *"); the answer is delivered on deliverTo, which defaults to channel (the channel the request came from). action=list returns the caller's schedules; action=cancel needs scheduleId.
schedule
Search across all entity types in the workspace. Returns matching results for clients, companies, invoices, and other entities. Use types to narrow results to a specific entity type.
search
Work with Subscription Templates. Subscription templates are reusable blueprints for creating subscriptions. Actions: list. List defaults to limit=25.
subscription_templates
Work with Subscriptions. Subscriptions are recurring billing schedules for clients. Actions: cancel, create, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: clientId, companyId, recipientId).
subscriptions
Work with Task Comments. Comments attached to tasks. Actions: delete, list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: taskId).
task_comments
Work with Task Templates. Task templates are reusable blueprints for creating tasks. Actions: list, retrieve. For single lookups prefer 'retrieve' with an id. List defaults to limit=25.
task_templates
Work with Tasks. Tasks track work items assigned to team members or clients. Actions: create, delete, list, retrieve, update. For single lookups prefer 'retrieve' with an id. List defaults to limit=25; use filter params to narrow results (filterable by: createdBy, parentTaskId, status, clientId, internalUserId, companyId).
tasks
Work with Workspaces. Workspaces are the top-level containers for all data in Assembly. Actions: retrieve
workspaces

FAQs

Assembly ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

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

As of 2026-11-12, Assembly competes with Assembled, Enclave, Gainsight Customer Communities, Velaris Basic, Velaris Intelligence in ChatGPT Customer Success 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.