- Brand
- Knottle
- Category
- Sales & CRM
- Primary Subcategory
- B2B Sales CRM Platforms
Integration details
Description
Knottleは、ChatGPTからCRM内の顧客、担当者、案件、活動、タスク、見積、請求を参照・作成・更新できる、日本の小規模事業者向けプラグインです。書き込み、発行、削除は操作種別が明示され、データはテナント単位で分離されます。Google DriveまたはDropboxへのファイル保存にも対応します。
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- B2B Sales CRM Platforms
- Secondary Subcategories
- None listed
- Brand
- Knottle
- Access
- Account required
- First tracked
- 2026-08-21
- Tool count
- 48
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Agent DiscoverabilityChatGPT Discoverability ScoreUpdated daily · 5 Oct 2026We’ve tracked this data every day since . That unbroken daily record makes the MCP Directory the most accurate view of MCPs across the core platforms.
0/100
Invisible#22of 39
in B2B Sales CRM Platforms- Picked
- 0.0/100
- Found
- 0.0/100
- Positioned
- –/100
Get alerts for Knottle
Get updates when Knottle’s Discoverability Score or category rank changes.
Competing in ChatGPT B2B Sales CRM Platforms
View Category48 tools agents can invoke
Accept a quote as the order for its deal (受注処理). Sets the deal to order stage. Refuses if the deal already has an accepted quote — the existing order acceptance must be cancelled first.
Mark a task as complete, or reopen it (done=false)
Create a new account (customer)
Create a correction revision of an issued invoice (訂正版の作成). Japanese e-bookkeeping law freezes the amounts and line items of an invoice once it has been issued, so a mistake on an issued invoice is corrected by making a revision rather than by editing it. This copies the header fields and every line item into a newly numbered revision of the same series, opened at the invoicing stage and unissued, and that revision becomes the current version — the one it was copied from stops being the current version and stays as history, still issued. The stage of the deal is brought back in line with the revision, and when that stage actually changes one activity entry is recorded automatically on the deal. This does NOT count towards the number of quotes created this month on the free plan, so it stays available even when that limit has been reached. Refused when the target is not the current version of its series, or when its invoice has not been issued.
Create a new deal linked to an account
Create a person (contact). If account_id is given, link to that account. When registering a contact from an email, extract and pass the details you can read — email, phone, mobile, job_title (役職), and department (部署) — from the signature/headers, not just the name. All are optional but storing them saves the user from re-typing.
Create a draft quote (with optional line items) for a deal. issued_at is NOT set (電帳法ロック回避). IMPORTANT: if the response contains `message`, relay it to the user verbatim — do not summarise, shorten or reword it. It states the quote number, total amount and line-item count of an existing unissued draft on the same deal, and asks whether the user meant to update that one instead. All four must survive; do not recompute the numbers yourself.
Create a task with optional due date and priority
Permanently delete an account and everything cascaded from it (案件・見積・見積明細) (取引先の削除). IRREVERSIBLE. Only allowed when EVERY quote under the account is unissued and is not the accepted order; if any quote is issued (as a quote or as an invoice) or is the accepted order, the delete is refused and the refusal names the quotes that are blocking it (undo the issue/acceptance first). Deleting cascades to the account's deals, quotes and quote line items, and removes document links (the underlying files in Google Drive / Dropbox are NOT deleted and remain in cloud storage). Contacts are not deleted by this call.
Permanently delete one activity record (活動の削除). IRREVERSIBLE — it cannot be restored afterwards. Only activities that were recorded by hand can be deleted; the ones the system wrote by itself (for example when a deal moved to another stage) are refused, exactly as they are refused on screen. Nothing else is removed — the account, the deal and the contact the activity was attached to all stay.
Permanently delete a deal and everything cascaded from it (見積・活動・タスク・書類リンク) (案件の削除). IRREVERSIBLE. Only allowed when EVERY quote on the deal is unissued and not the accepted order; if any quote is issued (as a quote or invoice) or is the accepted order, the delete is refused (undo the issue/acceptance first). Deleting cascades to the deal's quotes, activities and tasks, and removes document links (the underlying files in Google Drive / Dropbox are NOT deleted and remain in cloud storage).
Permanently delete a person (contact) (担当者の削除). IRREVERSIBLE. Removes the person and their links to companies; activities and tasks that referenced them are kept but lose the contact reference. There is no undo — recreate the contact if deleted by mistake.
Permanently delete a quote and its line items (見積の削除). IRREVERSIBLE. Only allowed when the quote is NOT issued (neither as a quote document nor as an invoice) and its series is NOT the accepted order. Otherwise the delete is refused: any recorded payment, the order acceptance, and the issuances must be undone first, in that order. The refusal message states the required order.
Delete a task permanently
Duplicate a quote into a new version (複製). Copies the header fields and every line item of the given quote into a newly numbered version of the same series, and that new version becomes the current one — the version it was copied from stops being the current version (it stays as history). Four things follow from this: the new version always opens unissued, so neither the quote document nor the invoice carries over any issue date; the stage of the deal is brought back in line with the new version; when that stage actually changes, one activity entry is recorded automatically on the deal; and on the free plan this counts as one of the quotes created this month, the same as creating a quote from scratch. Refused when the quote is not the current version of its series, when a payment has been recorded on it, or when the deal has been accepted for this series — the refusal states what has to be undone first. Use this to change the contents of an issued quote, which can no longer be edited in place.
Get a single account by ID with associated deals and people
Read the workspace's own company details and bank account (自社情報・振込先の取得). Returns the company name, address, phone number, Japanese invoice registration number (適格請求書発行事業者登録番号) and bank transfer details that appear on quotes and invoices. Fields that have not been filled in are returned as 未設定です rather than being omitted. Read-only: this changes nothing. There is no tool to update these — the customer sets them from the screen.
Get one deal by id. Returns the deal title, the company it belongs to, the stage, the amount together with where that amount comes from, the deal date, the notes, how the deal was registered, and whether the most recent change to it was made through this assistant or by a person working in the app.
Check whether this customer can save files to cloud storage right now, and where those files go. Knottle works with either Google Drive or Dropbox, and a customer may be using either one. The answer comes back in plain Japanese and can be passed on as written: whether storage is connected, whether saving will actually work, whether the connection expired and has to be re-authorised, and whether both storages are connected at once — a misconfiguration the customer must resolve in the settings screen. Never assume Google Drive: a Dropbox-only customer is fully connected and must not be told to connect Drive. Call this BEFORE encoding a file for upload. This is a hint only — saving enforces the same rules at save time.
Get one person (contact) by id, including the details that are not shown in a list: the reading of the name, the job title, the department, the mobile number, the fax number, the postal code, the address and the notes. Use it when the question is about a single contact rather than about a company.
Get a quote by id (with line items and deal/account).
Get links to the issued PDF documents of a quote (見積書・請求書のPDF). Returns a web link the customer can open in a browser for each document that has actually been issued — the quote document and the invoice are issued separately, so one may be available while the other is not. The file itself is never returned, only the link, so the contents cannot be read or summarised from here. When a document has not been issued yet there is no link for it, and the answer says so; issue it first if the customer needs it.
Check how much of the current allowance is left before creating more records (当月の残枠の確認). Returns two separate figures with different meanings: quotes are counted as a running total for the current month (deleting a quote does NOT give the count back; it resets next month), while accounts are counted as the number currently registered (deleting one does give the count back). Read-only: this changes nothing. Report the figures as they are returned and do not discuss billing.
Issue the invoice (請求書発行). IRREVERSIBLE side effect: this locks the invoice under 電帳法 (Japanese e-bookkeeping law) so line items and amounts can no longer be edited; correcting it requires creating a new revision. The issue date is the server date (JST) and cannot be supplied by the caller. A mistaken issue can be undone by cancelling the invoice issuance, but only after any recorded payment is undone and the order acceptance is cancelled.
Issue the quote document (見積書発行). Records the quote issue date as the server date (JST); the date cannot be supplied by the caller. This does NOT advance the pipeline status and does NOT apply the 電帳法 invoice lock (issuing the quote document and issuing the invoice are two separate, independent axes), but line items and amounts can no longer be edited afterwards; to change them, duplicate the quote into a new version.
List the accounts (companies) stored in this workspace, most recently updated first. No search text is required — call it with no arguments at all to see the accounts. Optional narrowing: a free-text query (matched against the company name, the notes and custom field values), and the status of the account (active, archived or lost). One page holds at most 20 accounts. The reply states how many accounts match in total, how many are in this page, and carries a continuation token when more remain — pass that token back as `cursor` to read the next page. Never present the accounts of one page as the whole list when a continuation token is present.
List activities (interactions like calls, emails, meetings, notes). account_id, deal_id and person_id are optional filters: omit all three to read the most recent activities across the entire workspace in one call, newest first. Returns at most 20 activities per page, together with the total number of matching activities; when more remain, pass the returned continuation value back as cursor to read the next page. Every row carries the deal name and the account name it belongs to.
List deals, optionally filtered by account_id. Returns at most 20 deals per page, most recently updated first, together with the total number of deals; when more remain, pass the returned continuation value back as cursor to read the next page.
List the files recorded for this customer, newest first. Filter by deal_id to answer 「この案件の書類は?」, or by account_id for everything filed under one company. With no filter it lists the whole tenant. category narrows it to one kind of paperwork (見積 / 契約書 / 現場写真 / 請求 / 音声メモ / その他). Returns at most 20 rows per page, plus the total number of matches and a 続き value; pass that value back as cursor to read the next page. Only files that are actually recorded are returned — if the answer is empty, say it is empty rather than assuming a file exists somewhere.
List tasks. For date ranges ("today", "this week", "by month-end"), pass full RFC 3339 datetimes with Z or a UTC offset in due_after / due_before; never pass a date-only YYYY-MM-DD value. Interpret the user's local time yourself because the server does not apply a timezone. Example: 2026-07-30 00:00 JST is 2026-07-29T15:00:00Z. Returns at most 20 tasks per page, most recently updated first (not by due date), together with the total number of matching tasks; when more remain, pass the returned continuation value back as cursor to read the next page.
Log an activity (call, email, meeting, note, etc.) for an account or deal
Record payment received for an invoice (入金記録). Requires the invoice to have been issued first — recording a payment on a quote whose invoice has not been issued is refused. Advances the quote to the paid stage. The deal itself only advances to the paid stage when this quote is the accepted order for that deal; if the deal has no accepted order, or a different quote of the deal was accepted, the deal stage is left as it is (and if another quote was accepted, this call is refused).
Upload a small file attachment (base64) to an account or deal. Saves to whichever cloud storage the customer has connected — Google Drive or Dropbox — into a 会社/案件/カテゴリ folder. Either one works; do not assume Google Drive. If no storage is connected (or both are, which is a misconfiguration), the call returns an error explaining what the customer has to do. Hard limit: 1MB per file — larger files are rejected, so do NOT send big files through chat. For files over the limit, tell the user to either (1) open the deal page in Knottle and use 「ファイルを選択」 to upload, or (2) save the file to their cloud storage and link it from the deal page. This tool is upload-only and never lists or links existing files.
Search accounts (customers). Searchable: the company name, the notes on the account, and custom field values. Not searchable: the industry (there is no industry field), and the deals or people that belong to the account. Matching is a partial, case-insensitive text match. One page holds at most 20 accounts. The reply states how many accounts match in total, how many are in this page, and carries a continuation token when more remain — pass that token back as `cursor` to read the next page.
Search across accounts, deals and people with a single query. Searchable: for accounts, the company name and notes; for deals, the deal title; for people, the full name, email, phone and mobile number; plus custom field values on all three. Not searchable: deal notes, and anything on the quotes (use the quote search for those). Returns at most 20 rows in total, shared fairly between the three kinds (a flood of matching companies will not crowd out the deals and people).
Search deals. Searchable: the deal title and custom field values. Not searchable: the deal notes, the company name, and the amounts — searching those returns nothing, so to find a deal by company, look the company up first and list its deals. Matching is a partial, case-insensitive text match. Returns at most 20 deals per page, most recently updated first, together with the total number of matches; when more remain, pass the returned continuation value back as cursor to read the next page.
Search quotes and invoices. Every argument is optional: call it with no arguments to get the most recently updated quotes of this tenant. Searchable: the quote number, the quote name, the customer name stored on the quote, the recipient name, the recipient department, and the notes on the quote. Not searchable: the deal title — a quote does NOT match on the name of the deal it belongs to. To find the quotes of a deal, look the deal up first and pass its id as deal_id (with any query); to get every quote of one company, pass account_id. Matching is a partial, case-insensitive text match. Filters: status is the stage of the quote (quote = 見積 / order = 受注 / invoice = 請求 / paid = 入金済), latest_only keeps only the newest version of each quote, and there are four independent date ranges — created_from/created_to (when the quote was created), quote_issued_from/quote_issued_to (when the quote document was issued to the customer), invoice_issued_from/invoice_issued_to (when the invoice was issued), and due_from/due_to (the payment due date). These four are different dates: pick the one the user actually means. A page holds at most 20 rows, newest first, and comes with the total number of matches and a cursor for the next page — read the next page before saying how many there are. Amounts are NOT totalled here: do not sum or estimate them.
Make a contact the primary contact of an account (主担当の設定). If the contact is not linked to the account yet, the link is created first, so this is also how a contact gets attached to a company as its main point of contact. An account keeps exactly one primary contact: whoever was primary before simply stops being primary — they are NOT removed from the account. Calling it again for the same contact changes nothing. An optional role (for example 経理担当) is stored on the link.
Cancel the order acceptance for a quote's deal (受注解除). Returns the deal to quote stage.
Undo an invoice issue (請求発行の取消). Reverts the invoice to draft — the 電帳法 issue lock is released and the status steps back one stage. Use this to fix a mistaken invoice issue. Two preconditions, both refused with a message stating the required order: (1) refused while a payment is recorded on the quote — the payment record must be undone first; (2) refused while the deal is accepted for this quote series — the order acceptance must be cancelled first.
Undo a quote issue (見積発行の取消). Clears the quote issue date. Line items and amounts become editable again ONLY if the invoice for this quote has not been issued: if the invoice is already issued, the 電帳法 (Japanese e-bookkeeping law) lock still applies and the line items stay frozen — correcting them then requires a correction revision, and the invoice issuance has to be undone first. Refused while the deal is accepted for this quote series — the order acceptance must be cancelled first.
Remove the link between a contact and an account (担当者の紐付け解除). IRREVERSIBLE — the role and the primary-contact mark stored on that link are lost and linking them again does not bring them back. The contact record itself is NOT deleted: they stay in the workspace and keep their other links. If the contact is not linked to that account, nothing is removed and the call is refused rather than reported as done.
Undo a recorded payment (入金記録の取消). Steps the quote and deal back one stage from paid to the invoice stage. This does NOT undo the invoice issuance itself — the invoice stays issued and locked under 電帳法 (Japanese e-bookkeeping law). Only possible when a payment has actually been recorded. This is the first step when unwinding a quote: while a payment is recorded, cancelling the invoice issuance is refused.
Update an existing account. All fields except id are optional.
Update an existing deal (title, stage, amount, deal_date, notes). All fields except id are optional.
Update an existing person (name, contact, fax, job info). All fields except id are optional.
Update a quote (line items, notes, status, header fields). Follows issue/sibling lock rules; will refuse edits to issued/locked quotes.
Update a task (title, description, priority, due date, status, account/deal links)
Knottle ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Knottle'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 Knottle alternatives on ChatGPT?
As of 2026-10-05, Knottle competes with HubSpot, Attio, Close, Zoho CRM, Agiled, Alaz, Asbie, Badger Maps (Advanced) and 30 more in ChatGPT B2B Sales CRM Platforms, ranked by public Discoverability Score.
Where does Knottle rank in B2B Sales CRM Platforms on ChatGPT?
As of 2026-10-05, Knottle ranks #22 of 39 in ChatGPT B2B Sales CRM Platforms with a Discoverability Score of 0/100 (Invisible).
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.