How to Search and Register SmartDB Documents with AI Chat | Connecting with the REST API and a Binder Token

When you keep requests and registers in SmartDB, you increasingly need to look things up, such as "How did we write the same request last year?" or "Who has borrowed this piece of equipment right now?" Opening a binder, choosing a view, entering conditions, and opening documents one at a time takes effort. This article is for administrators at companies that use SmartDB and the people who search its documents. It explains how to search documents in SmartDB binders from AI chat, and how to ask it to register and update them too.

It also covers how SmartDB's REST API works and what to decide when connecting it to AI.

The short answer

  • SmartDB has a REST API. It is an API for fetching and operating on SmartDB information from outside systems, and you can call it with a token issued under "Binder Tokens" in the admin screen. Operations called with the token are recorded as done by a robot user, not by a person, and they reach only the binders the token is set on
  • Samurai App's SmartDB integration can search and read documents in binders, and register and update documents. Only admins and managers can register and update, and by default a confirmation appears before it runs
  • It cannot delete documents, import or export CSV, or handle attachments, comments, or business processes (requests and approvals). Submitting, approving, or sending back a request is done in the SmartDB screens
  • Once connected, everyone in your Samurai App tenant can read the documents in the binders the token reaches. Which binders you set the token on is exactly what you expose

Three ways to work with SmartDB documents from outside

Search in the SmartDB screens Connect your own systems with the REST API or webhooks Work through the REST API from AI chat
What you need A SmartDB account Development of a mechanism that calls the API A binder token and an AI that supports API integrations
Best for Checking one document, requests and approvals Running a fixed process the same way every time Searching while changing conditions, registering a small number of documents
Who operates The person themselves The mechanism you built The token's robot user

In the SmartDB screens, you can switch views to search documents and handle requests and approvals right there. DreamArts says you can search even the text inside attachments and search across binders.

The REST API and webhooks are the integration methods listed in SmartDB's official documentation. The REST API is for fetching and operating on SmartDB information from outside systems, and webhooks call an external API when a document is registered, updated, or deleted, or when a workflow is approved. In both cases, you build the calling side yourself.

Working through the REST API from AI chat hands search and registration to an AI. You can search while rephrasing conditions, such as "last month's business trip requests" or "equipment on loan." Samurai App's SmartDB integration works this way.

Who acts when you operate with a binder token

When you call SmartDB's REST API with a token, the actor is not a person but a robot user for that token. The official API reference says it has permissions only on the binders the token is set on. If a field references another binder, the token must also be set on the referenced binder.

So documents registered or updated from Samurai App are recorded in SmartDB as registered or updated by the robot user. The name of the person who asked in chat is not kept in SmartDB's registrant field.

Note that the official API reference marks running with a binder token as "Binder API option only." Check your company's SmartDB contract to see whether you can use it.

What Samurai App can and cannot do

View (anyone can read binders the token reaches)

  • Search the binders it reaches
  • Read a binder's input fields (parts). You can see each part's name, type, whether it is required, and its options
  • List a binder's views
  • Search documents in a view. You can filter by part values or free text. Up to 100 per request (25 by default), and the rest are fetched page by page
  • Open one document and view its part values. You can also see who registered and who updated it

Register and update (admins and managers only; by default, a confirmation appears before it runs)

  • Register a document
  • Update a document's part values. Only the parts you change are sent, and the other parts stay as they are

What it cannot do

  • Delete documents
  • Import or export CSV
  • Attachments and comments
  • Business processes (requests and approvals). It cannot submit, approve, or send back a request
  • Register as a draft. A registered document goes in as a final document
  • View binders the token is not set on

Document searches always go through a view. Documents outside the view are not returned.

Using it to search and register request and register documents

SmartDB binders hold request records and registers as documents. From chat you can use them like this:

  • Search past requests to match how they were written. Ask "In the business trip request binder, search last year's documents with Osaka as the destination and list the purpose and amount." You can check how earlier ones were written before writing a new request. The request itself is submitted from the SmartDB screens
  • Check the current state of a register. Ask "In the equipment register, make a table of laptops on loan with who has borrowed them and the scheduled return date." You can also list overdue items first
  • Register one item in a register, or correct a value. Admins and managers can ask "Register the monitor we just bought in the equipment register" or "Set this document's status to returned." Add "Before registering, show me what goes into which part," and you can check the values before it proceeds

Registering and updating many documents means more confirmations to check, so keep requests in chat to a few at a time. For running a fixed process in bulk, SmartDB's CSV import or your own mechanism using the REST API is a better fit.

What you need

  • Someone who can use SmartDB's system administration screen (the person who issues the binder token), and the owner of each binder you want to expose
  • A Samurai App admin or manager (the person who connects SmartDB)
  • A rule for which binders everyone in your Samurai App tenant may read. Leave out binders with limited readers, such as HR or contracts

Steps

1. Issue a binder token in SmartDB and set it on binders

  1. Issue a token under "System Administration > Binder Tokens" in SmartDB
  2. For each binder you want it to reach, register this token in that binder's "Token Settings"
  3. Do not set "IP Address Restriction" on the token. Samurai App's source IP address is not fixed, so setting a restriction prevents it from connecting

If a reference field reads another binder, register the token on the referenced binder too.

2. The administrator connects SmartDB in Samurai App

Open the Connectors screen (/settings/connections) and press "Add API integration" on the "API integrations" tab. Choose SmartDB from the list of services.

In the "Subdomain" field, enter the part of the URL you use to open SmartDB from just after https:// up to the first ".". Paste the token from step 1 into the "Binder token" field and press "Connect to SmartDB."

When the connection is done, "Connected" is shown. Unlike other services, there is no step where each member registers their own account.

3. Ask in chat

In chat, be specific about which binder and which documents you want to search.

In the SmartDB equipment register binder, search for documents for laptops currently on loan,
and make a table of who has borrowed them and the scheduled return date. List overdue ones first

An admin or manager asks for registrations and updates.

Register the 2 monitors that arrived today in the equipment register, one document each.
Before registering, show me what goes into which part

A confirmation card appears before it runs. Read the parts and values, and allow it if everything looks right. When registration is done, the new document's number is returned.

Things to watch

Everyone in the tenant can read the binders the token reaches. On the Samurai App side, you cannot give different members access to different binders. Do not set this token on binders whose readers are limited in SmartDB.

The registrant becomes the robot user. If you want SmartDB to record who asked, add a part to the binder for the requester's name and have it filled in.

How parts and values are written differs by binder. Check on the confirmation card that dates and options follow the binder's rules before allowing it.

Disconnecting does not remove the token from SmartDB. When you press "Disconnect" in Samurai App, the stored token is discarded and SmartDB can no longer be used from chat. To disable the token itself, delete it in SmartDB's admin screen. The binders and documents in SmartDB stay as they are.

Frequently asked questions

Can I submit or approve requests from chat?

No. Business processes (requests and approvals) cannot be handled from chat. Use it to search and read request documents, and to register and update documents such as registers. Requests are submitted from the SmartDB screens.

Can members register documents too?

No. Members can search and read documents in the binders the token reaches, and no more. Only Samurai App admins and managers can register and update.

Can I operate as my own SmartDB account?

No. Operations from chat run as the binder token's robot user no matter who asks. For documents you want to view with your own permissions, or operations you want recorded under your own name, use the SmartDB screens.

Can I delete a document I registered by mistake?

Not from chat. Delete it in the SmartDB screens. If only a part value is wrong, you can fix it with an update from chat.

Where do I issue a binder token?

Issue it under "System Administration > Binder Tokens" in SmartDB and register it in the "Token Settings" of each binder you want it to reach. Ask someone who can use the system administration screen.

Sources

Based on DreamArts' SmartDB product site and product documentation as of November 9, 2026.

Related featureConnect business tools to AI over MCPSamurai App connects your business tools to AI over MCP. Operate accounting and HR SaaS from chat within each person's own permissions, call the agent from Slack or Teams, and use it from outside AI clients over MCP.

More automation examples

    Back to How-to articles

    Everyday work comes together, connects, and becomes the company's strength.

    Contact usOpen Samurai App

    See the demoContact us