Booqable MCP integration for AI agents.
Connect AI agents to Booqable through 10 structured actions, including get current company, get customer, and get order. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 10
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Booqable integration exposes
The Booqable Agent App exposes 10 provider-backed actions for productivity and data work. Its current contract lets an authorized agent fetch the current booqable company connected to the access token, fetch one booqable customer by id, and fetch one booqable order by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Booqable account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Booqable capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_companyREADFetch the current Booqable company connected to the access token.
INPUTS: fields / extraFields
get_customerREADFetch one Booqable customer by id.
INPUTS: customerId / fields / include
get_orderREADFetch one Booqable order by id.
INPUTS: orderId / fields / include
get_product_groupREADFetch one Booqable product group by id.
INPUTS: productGroupId / fields / include
list_customersREADList Booqable customers with optional fields, filters, includes, and paging.
INPUTS: fields / filter / include / meta / pageNumber
list_ordersREADList Booqable orders with optional fields, filters, includes, and paging.
INPUTS: fields / filter / include / meta / pageNumber
list_product_groupsREADList Booqable product groups with optional fields, filters, includes, and paging.
INPUTS: fields / filter / include / meta / pageNumber
search_customersREADRun a Booqable advanced search over customers.
INPUTS: search
search_ordersREADRun a Booqable advanced search over orders.
INPUTS: search
search_product_groupsREADRun a Booqable advanced search over product groups.
INPUTS: search
INPUT CONTRACTS
Know what the action needs before it runs.
get_current_company
fieldsOPTIONAL- Booqable fields keyed by resource type, for example { customers: "id,name" }.
extraFieldsOPTIONAL- Booqable extra fields keyed by resource type, for example { companies: "subscription" }.
get_customer
customerIdREQUIRED- The Booqable customer id.
fieldsOPTIONAL- Booqable fields keyed by resource type, for example { customers: "id,name" }.
includeOPTIONAL- Comma-separated Booqable relationships to sideload.
get_order
orderIdREQUIRED- The Booqable order id.
fieldsOPTIONAL- Booqable fields keyed by resource type, for example { customers: "id,name" }.
includeOPTIONAL- Comma-separated Booqable relationships to sideload.
get_product_group
productGroupIdREQUIRED- The Booqable product group id.
fieldsOPTIONAL- Booqable fields keyed by resource type, for example { customers: "id,name" }.
includeOPTIONAL- Comma-separated Booqable relationships to sideload.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current Company
Fetch the current Booqable company connected to the access token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_companyVerify with Get Customer
Fetch one Booqable customer by id. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_customerSAFETY BOUNDARY
Operate Booqable with explicit limits
- Authorize Booqable with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Booqable data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Booqable rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Booqable task completed successfully.
CONNECTION MODEL
API key
Booqable access token sent with the Authorization: Bearer header. Create access tokens from your Booqable account settings: https://developers.booqable.com/api/authentication.md.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Booqable.