Skip to the documentation
Ruby

client.knowledge

Every method in this namespace: its signature, its parameters, what it returns and an example.

Methods

The notes, files and web pages the AI uses when it writes replies, drafts email and answers in the assistant, each kept for the whole workspace, one domain or one address: list and search them, add a note, a link or a file, change, read again and delete them, and see the levels and how much the plan allows. Review the notes the AI suggests and the questions nothing answers, settle duplicate and conflict flags, keep a site, sitemap, feed or Zendesk help center in step with connectors, draft a note from a conversation, and read how often the AI used it.

knowledge.list

List one page of the knowledge base

Scopesknowledge:readPages through results
Signature
list(scope: nil, level: nil, kind: nil, status: nil, pinned: nil, q: nil, limit: nil, cursor: nil, api_key: nil) -> OpenEmail::Page

Returns one page of the knowledge base, newest first: the notes, files and web pages the AI uses when it writes replies, drafts email and answers in the assistant. Each item says where it sits, whether the AI can use it yet and how much text was read from it. list_all collects every page and iterate walks them lazily.

Every item sits at one level, its scope: an empty String for the whole workspace, @ and a domain for everything on that domain (@acme.com), or one address ([email protected]). The AI writing for an address reads that address, then its domain, then the whole workspace, the most specific first. level names the kind of level, workspace, domain or address.

status is queued or processing while the text is read and indexed, ready once the AI can use it, and failed with a failure when it could not be read. A key or an app limited to particular addresses sees the whole-workspace items and the items at its addresses and at their domains.

Each item also says how the AI uses it: uses counts the times it came up in a reply suggestion, a draft, the assistant or a search, with lastUsedAt the latest, and flags counts the open duplicate and conflict flags that name it. A link read again on a schedule has refreshDays and nextRefreshAt, a page kept by a connector names it in connectorId, and a note saved from a conversation names it in threadId.

Parameters

scopeString

Keeps the items at exactly this level: @ and a domain such as @acme.com, or one address. An empty String is not sent, so ask for the whole-workspace items with level: "workspace".

levelString

Keeps one kind of level: workspace, domain or address.

kindString

Keeps one kind of item: note, file or link.

statusString

Keeps one status: queued, processing, ready or failed.

pinnedBoolean

true keeps the pinned notes and false everything else.

qString

Words in the title, the file name or the link, matched without regard to case or accents.

limitInteger

Page size, from 1 to 100. The server defaults to 50.

cursorString

The next_cursor of the previous page. Leave it out for the first page.

api_keyString

Overrides the client API key for this call only.

Returns

An OpenEmail::Page of Hashes, with items, has_more? and next_cursor. Each item has id, kind, scope, level, title, url, fileName, mimeType, sizeBytes, pinned, status, failure, chunks, chars, origin, createdBy, createdAt, updatedAt, indexedAt, refreshDays, nextRefreshAt, connectorId, threadId, uses, lastUsedAt and flags.

Example

page = client.knowledge.list(level: "domain", kind: "file") page.items.each { |item| puts "#{item[:scope]} #{item[:title]} #{item[:status]}" }

Notes

  • Needs knowledge:read, which knowledge:write includes.

  • The cursor is opaque. One this list did not hand out is a 400 invalid_cursor. A scope that is neither a domain nor an address is a 422 invalid_knowledge_scope, and a level the key cannot see lists nothing.

Also available in

API
GET /knowledge
TypeScript
knowledge.list()
Python
knowledge.list()
PHP
knowledge->list
CLI
openemail knowledge list

knowledge.list_all

Collect every knowledge item into one array

Scopesknowledge:readPages through results
Signature
list_all(scope: nil, level: nil, kind: nil, status: nil, pinned: nil, q: nil, limit: nil, cursor: nil, api_key: nil) -> Array<Hash>

Walks every page of list and returns every item in one Array, newest first. One request per page, with the same filters on each.

Parameters

scopeString

Keeps the items at exactly this level: @ and a domain such as @acme.com, or one address. An empty String is not sent, so ask for the whole-workspace items with level: "workspace".

levelString

Keeps one kind of level: workspace, domain or address.

kindString

Keeps one kind of item: note, file or link.

statusString

Keeps one status: queued, processing, ready or failed.

pinnedBoolean

true keeps the pinned notes and false everything else.

qString

Words in the title, the file name or the link, matched without regard to case or accents.

limitInteger

Page size for each request, from 1 to 100. The server defaults to 50.

cursorString

Starts the walk after this cursor instead of the first page.

api_keyString

Overrides the client API key for every page of this walk.

Returns

An Array of Hashes holding every item, each with the fields list returns.

Example

failed = client.knowledge.list_all(status: "failed") failed.each { |item| puts "#{item[:title]}: #{item[:failure]}" }

Notes

  • If any page fails, the error is raised and the items already fetched are discarded.

Also available in

API
GET /knowledge
TypeScript
knowledge.listAll()
Python
knowledge.list_all()
PHP
knowledge->listAll

knowledge.iterate

Stream the knowledge items one at a time

Scopesknowledge:readPages through results
Signature
iterate(scope: nil, level: nil, kind: nil, status: nil, pinned: nil, q: nil, limit: nil, cursor: nil, api_key: nil, &block) -> Enumerator<Hash>

Returns an Enumerator that yields one item at a time, newest first, and requests the next page only once the current one is drained. Nothing is fetched until you consume it, and breaking out of the loop stops the requests. Given a block, it yields each item to the block instead.

Parameters

scopeString

Keeps the items at exactly this level: @ and a domain such as @acme.com, or one address. An empty String is not sent, so ask for the whole-workspace items with level: "workspace".

levelString

Keeps one kind of level: workspace, domain or address.

kindString

Keeps one kind of item: note, file or link.

statusString

Keeps one status: queued, processing, ready or failed.

pinnedBoolean

true keeps the pinned notes and false everything else.

qString

Words in the title, the file name or the link, matched without regard to case or accents.

limitInteger

Page size for each request, from 1 to 100. The server defaults to 50.

cursorString

Starts the walk after this cursor instead of the first page.

api_keyString

Overrides the client API key for every page of this walk.

Returns

An Enumerator of Hashes, one item per step (or yields each one to a block).

Example

client.knowledge.iterate(pinned: true) do |item|  puts "#{item[:scope].empty? ? "whole workspace" : item[:scope]} #{item[:title]}"end

Notes

  • Pages are fetched only as they are needed, so an abandoned loop costs only the pages you consumed.

Also available in

API
GET /knowledge
TypeScript
knowledge.iterate()
Python
knowledge.iterate()
PHP
knowledge->iterate

knowledge.levels

List the levels knowledge can sit at

Scopesknowledge:read
Signature
levels(api_key: nil) -> Array<Hash>

Returns every level the caller can see as an Array: the whole workspace first, then each domain, then each address, with how many items each holds and whether the caller may add and change items there. Pass its scope when you add an item.

A key or an app limited to particular addresses sees the whole workspace, its addresses and their domains. writable is true at the whole workspace only for a caller that reaches every address, at a domain for one that holds the whole domain, and at an address for one that holds that address.

Parameters

api_keyString

Overrides the client API key for this call only.

Returns

An Array of Hashes, each with scope, level, writable and items.

Example

levels = client.knowledge.levels p levels.select { |level| level[:writable] }.map { |level| level[:scope] }

Notes

  • Needs knowledge:read. A removed address is not a level.

Also available in

API
GET /knowledge/levels
TypeScript
knowledge.levels()
Python
knowledge.levels()
PHP
knowledge->levels
CLI
openemail knowledge levels

knowledge.usage

Read how much of the plan the knowledge base uses

Scopesknowledge:read
Signature
usage(api_key: nil) -> Hash

Returns how many items and how many characters of text the workspace keeps in its knowledge base, beside what its plan allows in limits: 50 items and 1,000,000 characters on Free, 500 and 10,000,000 on Starter, 2,000 and 50,000,000 on Business, and 10,000 and 200,000,000 on Enterprise.

An item counts as soon as it is added, and its characters once its text has been read. The numbers are for the whole workspace, whatever the key may reach.

Parameters

api_keyString

Overrides the client API key for this call only.

Returns

A Hash with plan, sources, chars and limits, which holds sources and chars.

Example

usage = client.knowledge.usage puts "#{usage[:sources]} of #{usage[:limits][:sources]} items, #{usage[:chars]} of #{usage[:limits][:chars]} characters"

Notes

  • Needs knowledge:read.

  • Adding an item to a full knowledge base is a 409 knowledge_allowance_reached. A file or a page whose text would pass the allowance once read is kept as failed, with failure: "over_allowance".

Also available in

API
GET /knowledge/usage
TypeScript
knowledge.usage()
Python
knowledge.usage()
PHP
knowledge->usage
CLI
openemail knowledge usage

knowledge.create_note

Add a note to the knowledge base

Scopesknowledge:write
Signature
create_note(body = nil, api_key: nil, **fields) -> Hash

Saves a note of up to 20,000 characters at one level and returns it. Markdown is kept, and its headings become the headings the passages sit under. A note is usually ready for the AI within a second or two, and queued or processing until then.

pinned: true puts the note into every prompt the AI writes at its level, not only when it matches what is being written. The AI reads at most 2,000 characters of pinned notes from each level, so keep them short.

Changing an item needs reach over every address its level covers: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address. A key or an app limited to particular addresses can change items only at those addresses, or at domains it holds whole.

Parameters

scopeString

The level: an empty String, or left out, for the whole workspace, @ and a domain such as @acme.com, or one address such as [email protected].

titleStringRequired

A short name for the note, at most 200 characters.

bodyStringRequired

The text, up to 20,000 characters, in Markdown if you like.

pinnedBoolean

Puts the note into every prompt at its level. Left out, false.

threadIdString

The conversation the note comes from, such as the one draft_from_thread read. It is kept on the note as threadId.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash for the new note, with kind: "note" and origin: "api".

Example

note = client.knowledge.create_note(  scope: "@acme.com",  title: "Refunds",  body: "Refunds are paid within 14 days of the return reaching our warehouse.",  pinned: true) puts note[:id], note[:status]

Notes

  • Needs knowledge:write.

  • A level that is not the workspace, one of its domains or one of its addresses is a 422 invalid_knowledge_scope, and a level outside what the key reaches is a 403 knowledge_scope_not_reached. A full knowledge base is a 409 knowledge_allowance_reached.

  • The SDK does not retry it, because a second attempt after a lost response could save the note twice. Look for it with list before trying again.

Also available in

API
POST /knowledge/notes
TypeScript
knowledge.createNote()
Python
knowledge.create_note()
PHP
knowledge->createNote
CLI
openemail knowledge create-note

knowledge.upload_file

Upload a file to the knowledge base

Scopesknowledge:write
Signature
upload_file(data, filename: nil, content_type: nil, scope: nil, title: nil, timeout: nil, api_key: nil) -> Hash

Stores a document or an image at one level and returns it, queued. Its text is read in the background, and the AI uses it once its status is ready. PDFs, Word documents, spreadsheets (Excel, OpenDocument, Numbers and CSV), OpenDocument text, HTML, XML, Markdown, plain text, JSON and images (JPEG, PNG, WebP and SVG) can be read.

data is a binary String (File.binread), an IO or a Pathname, sent as the request body. The name travels as the filename query parameter, and left out it falls back to an upload's original_filename or the file's own name, so only plain bytes need it. The type is content_type:, or an upload's own content_type, then the type the file's extension names. A document can be up to 20 MB and an image up to 10 MB.

Changing an item needs reach over every address its level covers: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address. A key or an app limited to particular addresses can change items only at those addresses, or at domains it holds whole.

Parameters

dataString, IO or PathnameRequired

The file, as a binary String, an IO or a Pathname, not empty, at most 20 MB for a document and 10 MB for an image.

filenameString

The file name, such as price-list.pdf. Its extension tells the kind of file when the type is generic. Left out, it is an upload's original_filename or the file's own name, so it is needed only for plain bytes. A missing or blank name raises an ArgumentError before anything is sent.

content_typeString

The MIME type, such as application/pdf. Left out, an upload's own content_type is used, else the type the file's extension names.

scopeString

The level: an empty String, or left out, for the whole workspace, @ and a domain such as @acme.com, or one address such as [email protected].

titleString

A name for the item, at most 200 characters. Left out, the file name without its extension.

timeoutNumeric

How long the upload may take, in seconds. Left out, it is 600 seconds (10 minutes), or the client timeout when that is longer. 0 waits as long as it takes.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash for the new file, with kind: "file", its fileName, mimeType and sizeBytes, and status: "queued".

Example

file = client.knowledge.upload_file(File.binread("report.pdf"), filename: "report.pdf", content_type: "application/pdf", scope: "[email protected]") puts file[:id], file[:title], file[:status]

Notes

Also available in

API
POST /knowledge/files
TypeScript
knowledge.uploadFile()
Python
knowledge.upload_file()
PHP
knowledge->uploadFile
CLI
openemail knowledge upload-file

knowledge.get

Read one knowledge item and its text

Scopesknowledge:read
Signature
get(id, api_key: nil) -> Hash

Returns one item with its text: the body of a note, or in preview the first 20,000 characters read from a file or a page, with previewTruncated true when the text goes on past it. preview is nil while a file or a page has not been read yet, and body is nil for anything but a note.

Parameters

idStringRequired

The id of the item, kb_ and 24 hex characters, as list returns it.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash with the fields list returns plus body, preview and previewTruncated.

Example

item = client.knowledge.get("kb_8c1f4a2b9d7e3f60a5c7b21d") puts item[:title], item[:body] || item[:preview]

Notes

  • Needs knowledge:read. An unknown id, and an item at a level the key cannot see, answer 404 knowledge_not_found.

Also available in

API
GET /knowledge/{id}
TypeScript
knowledge.get()
Python
knowledge.get()
PHP
knowledge->get
CLI
openemail knowledge get

knowledge.update

Change a knowledge item

Scopesknowledge:write
Signature
update(id, patch = nil, api_key: nil, **fields) -> Hash

Changes the title of an item, the text of a note, the page of a link, how often a link is read again, whether a note is pinned, or its level, and returns the item as it is now. Give at least one field. A changed title, text or link is read and indexed again, so the item goes back to queued, and its previous text stays in use until the new one is ready. Moving an item to another level needs no new reading.

Changing an item needs reach over every address its level covers: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address. A key or an app limited to particular addresses can change items only at those addresses, or at domains it holds whole. Moving an item needs that reach at both levels.

Parameters

idStringRequired

The id of the item, kb_ and 24 hex characters, as list returns it.

titleString

A new name, at most 200 characters.

bodyString

The new text of a note, up to 20,000 characters.

scopeString

The level to move it to: an empty String for the whole workspace, @ and a domain, or one address.

pinnedBoolean

Whether a note goes into every prompt at its level.

urlString

The new page of a link, a public http or https address.

refreshDaysInteger

Reads a link again every 1, 7 or 30 days, counted from now. nil stops that.

api_keyString

Overrides the client API key for this call only.

Returns

The item Hash as it is now, shaped like the one list returns.

Example

item = client.knowledge.update(  "kb_8c1f4a2b9d7e3f60a5c7b21d",  body: "Refunds are paid within 10 days of the return reaching our warehouse.",  pinned: true) puts item[:status], item[:updatedAt]

Notes

Also available in

API
PATCH /knowledge/{id}
TypeScript
knowledge.update()
Python
knowledge.update()
PHP
knowledge->update
CLI
openemail knowledge update

knowledge.delete

Delete a knowledge item for good

Scopesknowledge:write
Signature
delete(id, api_key: nil) -> Hash

Removes an item with its file and every passage read from it, and the AI stops using it at once. There is no undo.

Parameters

idStringRequired

The id of the item, kb_ and 24 hex characters, as list returns it.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash with object: "knowledge_item", id and deleted: true.

Example

removed = client.knowledge.delete("kb_8c1f4a2b9d7e3f60a5c7b21d") puts removed[:deleted]

Notes

  • Needs knowledge:write, and reach over the level of the item. An unknown id is a 404 knowledge_not_found.

  • The SDK does not retry a delete. A 404 on your own second attempt after a lost response means the first one worked.

Also available in

API
DELETE /knowledge/{id}
TypeScript
knowledge.delete()
Python
knowledge.delete()
PHP
knowledge->delete
CLI
openemail knowledge delete

knowledge.refresh

Read a knowledge item again

Scopesknowledge:write
Signature
refresh(id, api_key: nil) -> Hash

Fetches a link again, reads a file again or indexes a note again, clears any failure and returns the item, back at queued. Use it after a page changed or when an item failed. The previous text stays in use until the new one is ready.

Parameters

idStringRequired

The id of the item, kb_ and 24 hex characters, as list returns it.

api_keyString

Overrides the client API key for this call only.

Returns

The item Hash, queued to be read again.

Example

item = client.knowledge.refresh("kb_8c1f4a2b9d7e3f60a5c7b21d") puts item[:status]

Notes

  • Needs knowledge:write, and reach over the level of the item.

  • Reading an item again twice leaves it the same way, so the SDK retries it on network failure and retryable statuses.

Also available in

API
POST /knowledge/{id}/refresh
TypeScript
knowledge.refresh()
Python
knowledge.refresh()
PHP
knowledge->refresh
CLI
openemail knowledge refresh

knowledge.stats

Read how the AI used the knowledge base

Scopesknowledge:read
Signature
stats(days: nil, api_key: nil) -> Hash

Returns how the AI used the knowledge base over the last days days, today included, 30 unless you say. uses counts the times a reply suggestion, a draft, the assistant or a search found something in it, and empty the times it looked and found nothing. coverage is uses divided by the two together, from 0 to 1, and 0 when it never looked. bySurface splits uses by where they happened, under the keys compose, reply, chat, tool and search, and series has one entry per day, oldest first, days with nothing included.

topItems lists the items used most, ever, and unusedItems counts the ready items the AI has never used. pendingSuggestions counts the learned notes waiting for review, openQuestions the questions senders asked that nothing answers yet, and openFlags the open duplicate and conflict flags. uses, empty, bySurface and series cover the whole workspace, while the items, suggestions, questions and flags count only what the caller can see.

Parameters

daysInteger

How many days back to count, today included, from 1 to 90. The server defaults to 30.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash with days, uses, empty, coverage, bySurface, series, topItems, unusedItems, pendingSuggestions, openQuestions and openFlags. Each day in series has day, uses and empty, and each of topItems has id, title, kind, scope, uses and lastUsedAt.

Example

stats = client.knowledge.stats(days: 7) puts "#{(stats[:coverage] * 100).round}% of lookups found something"stats[:topItems].each { |item| puts "#{item[:uses]} #{item[:title]}" }

Notes

  • Needs knowledge:read. It changes nothing, so the SDK retries it like any other read.

  • A days outside 1 to 90 is a 422 invalid_parameter.

Also available in

API
GET /knowledge/stats
TypeScript
knowledge.stats()
Python
knowledge.stats()
PHP
knowledge->stats
CLI
openemail knowledge stats

knowledge.list_suggestions

List one page of knowledge suggestions and questions

Scopesknowledge:readPages through results
Signature
list_suggestions(kind: nil, status: nil, limit: nil, cursor: nil, api_key: nil) -> OpenEmail::Page

Returns one page of what the AI suggests adding to the knowledge base, the most recent first, pending ones unless you ask for another status. list_all_suggestions collects every page and iterate_suggestions walks them lazily.

A learned suggestion is a note the AI drew from a reply sent from the workspace: it reads the message the reply answers and the reply, and keeps up to three facts that would hold for other people too, at the level of the domain the reply was sent from, or the whole workspace when that domain is not one of its own. Facts the knowledge base already holds are left out, and at most 100 replies a day are read. A question is something a sender asked about the business that neither the conversation nor the knowledge base answers: when the AI suggests replies to an incoming message, it notes up to 3 such questions, at the level of the domain the message arrived at, chosen the same way. Accept a question with its answer and it becomes a note.

The same fact or question again counts up occurrences instead of adding a second suggestion, and one that was dismissed is not suggested again. Both kinds stop while the workspace setting knowledgeLearning is off, which settings.update changes.

Parameters

kindString

Keeps one kind: learned for notes drawn from sent replies, or question for questions nothing answers.

statusString

Keeps one status: pending, accepted or dismissed. Left out, pending.

limitInteger

Page size, from 1 to 100. The server defaults to 50.

cursorString

The next_cursor of the previous page. Leave it out for the first page.

api_keyString

Overrides the client API key for this call only.

Returns

An OpenEmail::Page of Hashes, with items, has_more? and next_cursor. Each suggestion has id, kind, status, scope, level, title, body, occurrences, threadId, sourceId, createdAt, updatedAt and decidedAt.

Example

page = client.knowledge.list_suggestions(kind: "question") page.items.each { |question| puts "#{question[:occurrences]} #{question[:title]}" }

Notes

  • Needs knowledge:read, which knowledge:write includes.

  • A learned suggestion holds the suggested note in title and body. A question holds the question in title, and its body is nil until it is answered. threadId names the conversation it came from most recently, and sourceId the note made from it once it is accepted.

  • A key or an app limited to particular addresses sees the suggestions at the whole workspace, at its addresses and at their domains. The cursor is opaque, and one this list did not hand out is a 400 invalid_cursor.

Also available in

API
GET /knowledge/suggestions
TypeScript
knowledge.listSuggestions()
Python
knowledge.list_suggestions()
PHP
knowledge->listSuggestions
CLI
openemail knowledge list-suggestions

knowledge.list_all_suggestions

Collect every knowledge suggestion into one array

Scopesknowledge:readPages through results
Signature
list_all_suggestions(kind: nil, status: nil, limit: nil, cursor: nil, api_key: nil) -> Array<Hash>

Walks every page of list_suggestions and returns every suggestion or question that matches in one Array, the most recent first. One request per page, with the same filters on each.

Parameters

kindString

Keeps one kind: learned for notes drawn from sent replies, or question for questions nothing answers.

statusString

Keeps one status: pending, accepted or dismissed. Left out, pending.

limitInteger

Page size for each request, from 1 to 100. The server defaults to 50.

cursorString

Starts the walk after this cursor instead of the first page.

api_keyString

Overrides the client API key for every page of this walk.

Returns

An Array of Hashes holding every suggestion and question that matches, each with the fields list_suggestions returns.

Example

questions = client.knowledge.list_all_suggestions(kind: "question") puts "#{questions.size} questions wait for an answer"

Notes

  • If any page fails, the error is raised and the suggestions already fetched are discarded.

Also available in

API
GET /knowledge/suggestions
TypeScript
knowledge.listAllSuggestions()
Python
knowledge.list_all_suggestions()
PHP
knowledge->listAllSuggestions

knowledge.iterate_suggestions

Stream the knowledge suggestions one at a time

Scopesknowledge:readPages through results
Signature
iterate_suggestions(kind: nil, status: nil, limit: nil, cursor: nil, api_key: nil, &block) -> Enumerator<Hash>

Returns an Enumerator that yields one suggestion or question at a time, the most recent first, and requests the next page only once the current one is drained. Nothing is fetched until you consume it, and breaking out of the loop stops the requests. Given a block, it yields each one to the block instead.

Parameters

kindString

Keeps one kind: learned for notes drawn from sent replies, or question for questions nothing answers.

statusString

Keeps one status: pending, accepted or dismissed. Left out, pending.

limitInteger

Page size for each request, from 1 to 100. The server defaults to 50.

cursorString

Starts the walk after this cursor instead of the first page.

api_keyString

Overrides the client API key for every page of this walk.

Returns

An Enumerator of Hashes, one suggestion or question per step (or yields each one to a block).

Example

client.knowledge.iterate_suggestions(kind: "learned") do |suggestion|  puts "#{suggestion[:scope].empty? ? "whole workspace" : suggestion[:scope]} #{suggestion[:title]}"end

Notes

  • Pages are fetched only as they are needed, so an abandoned loop costs only the pages you consumed.

Also available in

API
GET /knowledge/suggestions
TypeScript
knowledge.iterateSuggestions()
Python
knowledge.iterate_suggestions()
PHP
knowledge->iterateSuggestions

knowledge.accept_suggestion

Save a knowledge suggestion as a note

Scopesknowledge:write
Signature
accept_suggestion(id, body = nil, api_key: nil, **fields) -> Hash

Saves a pending suggestion or question as a note, marks it accepted and returns both: the suggestion, its sourceId naming the new note, and the note itself in item. Any field you send takes the place of the suggested one, so you can tidy the title, rewrite the text, move it to another level or pin it on the way in. The note keeps the conversation the suggestion came from in threadId.

A question needs its answer in body, and its title stays the question unless you send one. Answering a question this way is how it becomes a note the AI uses from then on.

Changing an item needs reach over every address its level covers: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address. A key or an app limited to particular addresses can change items only at those addresses, or at domains it holds whole.

Parameters

idStringRequired

The id of the suggestion or question, kp_ and 24 hex characters, as list_suggestions returns it.

titleString

A title for the note, at most 200 characters. Left out, the suggested title or the question.

bodyString

The text of the note, up to 20,000 characters. Left out, the suggested note. A question needs it: the answer.

scopeString

The level for the note: an empty String for the whole workspace, @ and a domain, or one address. Left out, the suggested level.

pinnedBoolean

Puts the note into every prompt at its level. Left out, false.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash with object: "knowledge_suggestion_accepted", suggestion, now accepted, and item, the new note shaped like the items list returns.

Example

accepted = client.knowledge.accept_suggestion("kp_3f9a1c7e5b2d8046a1c3e5f7", body: "Orders over 50 euros ship free within the EU.") puts accepted[:item][:id], accepted[:item][:status]

Notes

Also available in

API
POST /knowledge/suggestions/{id}/accept
TypeScript
knowledge.acceptSuggestion()
Python
knowledge.accept_suggestion()
PHP
knowledge->acceptSuggestion
CLI
openemail knowledge accept-suggestion

knowledge.dismiss_suggestion

Dismiss a knowledge suggestion or question

Scopesknowledge:write
Signature
dismiss_suggestion(id, api_key: nil) -> Hash

Marks a pending suggestion or question dismissed and returns it. It leaves the pending list, the same fact or question is not suggested again, and nothing is added to the knowledge base.

Dismissing needs the reach to add a note at the level of the suggestion: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address.

Parameters

idStringRequired

The id of the suggestion or question, kp_ and 24 hex characters, as list_suggestions returns it.

api_keyString

Overrides the client API key for this call only.

Returns

The suggestion Hash with status: "dismissed" and decidedAt set.

Example

dismissed = client.knowledge.dismiss_suggestion("kp_3f9a1c7e5b2d8046a1c3e5f7") puts dismissed[:status], dismissed[:decidedAt]

Notes

Also available in

API
POST /knowledge/suggestions/{id}/dismiss
TypeScript
knowledge.dismissSuggestion()
Python
knowledge.dismiss_suggestion()
PHP
knowledge->dismissSuggestion
CLI
openemail knowledge dismiss-suggestion

knowledge.list_flags

List the open duplicate and conflict flags

Scopesknowledge:read
Signature
list_flags(item_id: nil, limit: nil, api_key: nil) -> Array<Hash>

Returns the open warnings about pairs of knowledge items as one Array, newest first. Each item is compared with the closest items at every level when it is indexed, and again whenever it changes. duplicate means the two items say nearly the same thing. conflict means the AI found that two closely related items disagree on a fact, such as a price or a deadline, and detail says how in one sentence. The AI looks for conflicts while the workspace setting knowledgeLearning is on, at most 200 times a day.

Change or delete one of the two items to settle a flag: a changed item is compared again once it is indexed, and the flags of a deleted item go with it. When the two are fine as they are, dismiss the flag with dismiss_flag. A flag shows only to a caller who can see both items.

Parameters

item_idString

Keeps the flags that name this knowledge item, on either side.

limitInteger

How many flags, from 1 to 100. The server defaults to 50.

api_keyString

Overrides the client API key for this call only.

Returns

An Array of Hashes, each with id, kind, status, sourceId, sourceTitle, otherSourceId, otherSourceTitle, detail, score and createdAt. score is how close in meaning the two items are, from 0 to 1.

Example

flags = client.knowledge.list_flags flags.each { |flag| puts "#{flag[:kind]}: #{flag[:sourceTitle]} and #{flag[:otherSourceTitle]}" }

Notes

  • Needs knowledge:read. Every item also carries flags, the number of open flags that name it, so list shows which items to look at.

  • Only open flags are listed. A dismissed flag stays dismissed, and the same two items are not flagged for the same reason again.

Also available in

API
GET /knowledge/flags
TypeScript
knowledge.listFlags()
Python
knowledge.list_flags()
PHP
knowledge->listFlags
CLI
openemail knowledge list-flags

knowledge.dismiss_flag

Dismiss a duplicate or conflict flag

Scopesknowledge:write
Signature
dismiss_flag(id, api_key: nil) -> Hash

Marks a flag dismissed when the two items are fine as they are, and returns it. The same two items are not flagged for the same reason again. To settle a real duplicate or conflict instead, change or delete one of the items.

Dismissing needs the reach to change items at the levels of both items: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address.

Parameters

idStringRequired

The id of the flag, kf_ and 24 hex characters, as list_flags returns it.

api_keyString

Overrides the client API key for this call only.

Returns

The flag Hash with status: "dismissed".

Example

flag = client.knowledge.dismiss_flag("kf_7b3d9e1f5a2c8046b1d3e5f7") puts flag[:status]

Notes

  • Needs knowledge:write. An unknown id, and a flag on an item the key cannot see, answer 404 knowledge_flag_not_found, and an item the key may not change is a 403 knowledge_scope_not_reached.

  • Dismissing a flag twice leaves it the same way, so the SDK retries it on network failure and retryable statuses.

Also available in

API
POST /knowledge/flags/{id}/dismiss
TypeScript
knowledge.dismissFlag()
Python
knowledge.dismiss_flag()
PHP
knowledge->dismissFlag
CLI
openemail knowledge dismiss-flag

knowledge.list_connectors

List the knowledge connectors

Scopesknowledge:read
Signature
list_connectors(api_key: nil) -> Array<Hash>

Returns every connector at a level the caller can see as one Array, newest first. A connector keeps many web pages from one source in the knowledge base, each page as a link item at the connector's level: a site it crawls, a sitemap, an RSS or Atom feed, or a Zendesk help center. Each one says how many items it keeps, its status, when it last synced and when it syncs next.

Parameters

api_keyString

Overrides the client API key for this call only.

Returns

An Array of Hashes, each with id, kind, scope, level, title, url, refreshDays, pageLimit, status, failure, items, lastSyncAt, nextSyncAt, createdAt and updatedAt.

Example

connectors = client.knowledge.list_connectors connectors.each { |connector| puts "#{connector[:kind]} #{connector[:url]} #{connector[:items]} #{connector[:status]}" }

Notes

  • Needs knowledge:read. A key or an app limited to particular addresses sees the connectors at the whole workspace, at its addresses and at their domains.

  • The items a connector keeps show in list too, each with connectorId naming it.

Also available in

API
GET /knowledge/connectors
TypeScript
knowledge.listConnectors()
Python
knowledge.list_connectors()
PHP
knowledge->listConnectors
CLI
openemail knowledge list-connectors

knowledge.add_connector

Keep the pages of a site, sitemap, feed or help center

Scopesknowledge:write
Signature
add_connector(body = nil, api_key: nil, **fields) -> Hash

Adds a connector at one level and returns it, queued. Its first sync starts within a minute, and every page it finds becomes a link item at the connector's level, read in the background like any other link.

site reads the page at url and follows its links to pages on the same host under the same path, leaving out what the site's robots.txt disallows. sitemap reads a sitemap, or a sitemap index and up to 5 of its sitemaps. feed reads an RSS or Atom feed. zendesk reads the published articles of a Zendesk help center from its address, such as https://example.zendesk.com.

It keeps at most pageLimit pages, 25 unless you say, and syncs again every refreshDays days, 7 unless you say: new pages are added, changed ones are read again and the items of pages that are gone are removed. A page already in the knowledge base as a link at the same level is left to that item. Its items count toward the plan allowance, and a sync stops adding pages once that is reached.

Changing an item needs reach over every address its level covers: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address. A key or an app limited to particular addresses can change items only at those addresses, or at domains it holds whole.

Parameters

kindStringRequired

What url is: site, sitemap, feed or zendesk.

urlStringRequired

A public web address of at most 2,048 characters, kept as https: the page a site crawl starts from, the sitemap, the feed, or the address of the help center.

scopeString

The level: an empty String, or left out, for the whole workspace, @ and a domain such as @acme.com, or one address such as [email protected].

titleString

A name for the connector, at most 200 characters. Left out, the host and the kind, such as acme.com (sitemap).

refreshDaysInteger

Sync again every 1, 7 or 30 days. Left out, 7. nil syncs only when you call sync_connector.

pageLimitInteger

The most pages to keep, from 1 to 200. Left out, 25.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash for the new connector, with status: "queued" and items: 0.

Example

docs = client.knowledge.add_connector(kind: "sitemap", url: "https://acme.com/sitemap.xml", scope: "@acme.com", pageLimit: 100) puts docs[:id], docs[:status]

Notes

  • Needs knowledge:write.

  • An address that is not a public web address is a 422 invalid_knowledge_connector, and the same address at the same level a 409 knowledge_connector_exists. A refreshDays other than 1, 7, 30 or nil is a 422 invalid_knowledge_refresh. A level that is not the workspace, one of its domains or one of its addresses is a 422 invalid_knowledge_scope, and a level outside what the key reaches is a 403 knowledge_scope_not_reached.

  • A source that cannot be read after several tries ends failed with a failure. A sync that stopped at the plan allowance ends ready with failure: "over_allowance", and one that found nothing ends ready with failure: "empty".

  • The SDK does not retry it. A second attempt after a lost response answers 409 knowledge_connector_exists, which means the first one worked.

Also available in

API
POST /knowledge/connectors
TypeScript
knowledge.addConnector()
Python
knowledge.add_connector()
PHP
knowledge->addConnector
CLI
openemail knowledge add-connector

knowledge.get_connector

Read one knowledge connector

Scopesknowledge:read
Signature
get_connector(id, api_key: nil) -> Hash

Returns one connector: its source, its level, how many items it keeps, its status, and when it last synced and syncs next. status is queued until a sync starts, syncing while it reads the source, ready once its pages are items, and failed with a failure when the source could not be read after several tries.

Parameters

idStringRequired

The id of the connector, kc_ and 24 hex characters, as list_connectors returns it.

api_keyString

Overrides the client API key for this call only.

Returns

The connector Hash, shaped like the ones list_connectors returns.

Example

connector = client.knowledge.get_connector("kc_5d2e8f1a3c7b9064e2a4c6f8") puts connector[:status], connector[:items], connector[:nextSyncAt]

Notes

Also available in

API
GET /knowledge/connectors/{id}
TypeScript
knowledge.getConnector()
Python
knowledge.get_connector()
PHP
knowledge->getConnector
CLI
openemail knowledge get-connector

knowledge.update_connector

Change a knowledge connector

Scopesknowledge:write
Signature
update_connector(id, patch = nil, api_key: nil, **fields) -> Hash

Changes the title of a connector, its level, how often it syncs or the most pages it keeps, and returns it as it is now. Give at least one field. Moving it to another level moves its items with it, and they are indexed again there. A new refreshDays counts from the last sync, and a new pageLimit applies from the next sync.

Changing an item needs reach over every address its level covers: the whole workspace needs every address, a domain needs the whole domain, and an address needs that address. A key or an app limited to particular addresses can change items only at those addresses, or at domains it holds whole. Moving a connector needs that reach at both levels.

Parameters

idStringRequired

The id of the connector, kc_ and 24 hex characters, as list_connectors returns it.

titleString

A new name, at most 200 characters.

scopeString

The level to move it and its items to: an empty String for the whole workspace, @ and a domain, or one address.

refreshDaysInteger

Sync every 1, 7 or 30 days. nil syncs only when you call sync_connector.

pageLimitInteger

The most pages to keep, from 1 to 200.

api_keyString

Overrides the client API key for this call only.

Returns

The connector Hash as it is now.

Example

connector = client.knowledge.update_connector("kc_5d2e8f1a3c7b9064e2a4c6f8", refreshDays: 1, pageLimit: 150) puts connector[:nextSyncAt]

Notes

  • Needs knowledge:write. An empty patch is a 422 invalid_parameter, and a refreshDays other than 1, 7, 30 or nil a 422 invalid_knowledge_refresh. Moving it to a level that already has a connector for the same address is a 409 knowledge_connector_exists.

  • Retried automatically on network failure and retryable statuses, since the same patch applied twice leaves the same connector.

Also available in

API
PATCH /knowledge/connectors/{id}
TypeScript
knowledge.updateConnector()
Python
knowledge.update_connector()
PHP
knowledge->updateConnector
CLI
openemail knowledge update-connector

knowledge.delete_connector

Delete a knowledge connector and its items

Scopesknowledge:write
Signature
delete_connector(id, api_key: nil) -> Hash

Removes a connector with every item it added to the knowledge base, and the AI stops using them at once. There is no undo. Links you added yourself stay, even when the connector found the same pages.

Parameters

idStringRequired

The id of the connector, kc_ and 24 hex characters, as list_connectors returns it.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash with object: "knowledge_connector", id and deleted: true.

Example

removed = client.knowledge.delete_connector("kc_5d2e8f1a3c7b9064e2a4c6f8") puts removed[:deleted]

Notes

  • Needs knowledge:write, and reach over the level of the connector. An unknown id is a 404 knowledge_connector_not_found.

  • The SDK does not retry a delete. A 404 on your own second attempt after a lost response means the first one worked.

Also available in

API
DELETE /knowledge/connectors/{id}
TypeScript
knowledge.deleteConnector()
Python
knowledge.delete_connector()
PHP
knowledge->deleteConnector
CLI
openemail knowledge delete-connector

knowledge.sync_connector

Sync a knowledge connector now

Scopesknowledge:write
Signature
sync_connector(id, api_key: nil) -> Hash

Queues a sync that starts within a minute, whatever the schedule says, clears any failure and returns the connector, back at queued. Use it after the source changed, or to try again after a failure. Like a scheduled sync, it adds new pages, reads changed ones again and removes the items of pages that are gone.

Parameters

idStringRequired

The id of the connector, kc_ and 24 hex characters, as list_connectors returns it.

api_keyString

Overrides the client API key for this call only.

Returns

The connector Hash, queued to sync.

Example

connector = client.knowledge.sync_connector("kc_5d2e8f1a3c7b9064e2a4c6f8") puts connector[:status]

Notes

  • Needs knowledge:write, and reach over the level of the connector. An unknown id is a 404 knowledge_connector_not_found.

  • Queuing a sync twice leaves it the same way, so the SDK retries it on network failure and retryable statuses.

Also available in

API
POST /knowledge/connectors/{id}/sync
TypeScript
knowledge.syncConnector()
Python
knowledge.sync_connector()
PHP
knowledge->syncConnector
CLI
openemail knowledge sync-connector

knowledge.draft_from_thread

Draft a knowledge note from a conversation

Scopesknowledge:writethreads:read
Signature
draft_from_thread(body = nil, api_key: nil, **fields) -> Hash

The AI reads a conversation and drafts one note of the facts in it that the team will need again, leaving out personal details and what matters only to that conversation. Nothing is saved: the draft comes back with a title, a body in Markdown and a scope it suggests, and you keep it, changed as you like, with create_note and the same threadId.

scope suggests the domain the conversation arrived at when the caller may add items there, otherwise the whole workspace or the address itself. Each draft counts as one AI action.

Parameters

threadIdStringRequired

The conversation, by the id threads.list gives it.

api_keyString

Overrides the client API key for this call only.

Returns

A Hash with object: "knowledge_draft", title, body, scope and threadId.

Example

draft = client.knowledge.draft_from_thread(threadId: "CAHk7pQ2x9LmZ4-mail.example.com") note = client.knowledge.create_note(scope: draft[:scope], title: draft[:title], body: draft[:body], threadId: draft[:threadId]) puts note[:id], note[:threadId]

Notes

Also available in

API
POST /knowledge/drafts
TypeScript
knowledge.draftFromThread()
Python
knowledge.draft_from_thread()
PHP
knowledge->draftFromThread
CLI
openemail knowledge draft-from-thread