Integration
Connect Casebook to Plentyone
When New Case fires in Casebook, your agent runs Add contact in Plentyone. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Casebook and Plentyone to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Casebook can start in Plentyone
When New Case in Casebook
then Add contact in Plentyone
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Casebook and Plentyone
Triggers and actions 3 triggers · 34 actions
- New Case
Triggers when a new case is created in Casebook.
- New Intake Report
Triggers when a new intake report is created in Casebook.
- New Person
Triggers when a new person is created in Casebook.
- Add a Person to a Case
Adds a person to a Casebook case.
- Create a Case
Creates a new case in Casebook with a name, description and case type.
- Create an Intake Report
Creates a new intake report in Casebook with a name, narrative and report type.
- Create a Note
Creates a note in Casebook, optionally attached to a person, case or other record.
- Create a Person
Creates a new person in Casebook with their name and basic demographics.
- Create a Provider
Creates a new provider in Casebook with a name and contact details.
- Delete a Person
Deletes a person in Casebook. The record is hidden from view, not permanently purged.
- Find People
Finds Casebook people by first name, last name or date of birth and returns the first match.
- Get a Case
Returns one Casebook case by ID, including its name and description.
- Get an Intake Report
Returns one Casebook intake report by ID, including its name, narrative and when it was reported.
- Get a Person
Returns one Casebook person by ID, including name, date of birth and other demographics.
- Get a Provider
Returns one Casebook provider by ID, including its name, email and phone number.
- Update a Case
Updates a Casebook case's name, description or goals. Only the fields you fill in are changed.
- Update a Person
Updates a Casebook person's name or demographics. Only the fields you fill in are changed.
- Add contact
Creates a new contact (a person) in the plentyONE CRM.
- Add item
Creates an item in plentyONE together with its main variation, linked to a category and a unit.
- Add order
Creates an order (sales order, return, offer and other order types) in plentyONE with its items, addresses and contact relations.
- Add payment
Creates a payment in plentyONE, for example an incoming payment received through a payment method.
- Add variation
Creates a new variation of an existing item, optionally defined by attribute values and made visible in a store client.
- Find items by criteria
Finds items updated on or after a given time, optionally including their variations.
- Find orders by criteria
Finds orders matching criteria such as order type, status, creation or update date, referrer, item or variation.
- Get contact
Returns a single contact (person) from the plentyONE CRM by its id.
- Get item
Returns a single plentyONE item, including its global settings, free fields and main variation id.
- Get order
Returns a single order by its id, including its amounts, properties, addresses and order items.
- Get payment
Returns a single payment by its id, including amount, currency, payment method, status and properties.
- List categories
Returns the categories set up in PlentyONE, optionally only those of one type such as item categories.
- List contacts
Returns the contacts (people) saved in your PlentyONE system, with their contact options and linked accounts.
- List stock
Returns the stock levels of variations across all warehouses.
- List variations
Returns the variations of an item, including its main variation.
- List warehouses
Returns all warehouses set up in your PlentyONE system.
- Update contact
Updates an existing contact (person) in PlentyONE CRM. Only the fields you fill in are changed.
- Update item
Updates the item-level settings of an existing plentyONE item, such as manufacturer, condition, flags and customs data.
- Update order
Updates an existing plentyONE order, such as its status, owner, properties, dates, addresses or order items.
- Update variation
Updates an existing variation of an item in plentyONE, such as its number, availability, dimensions, weight or order quantities.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Casebook
Casebook to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Casebook to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Casebook to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Casebook to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Casebook to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Casebook to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Plentyone
Questions
Casebook and Plentyone, answered
What can start an automation from Casebook?
Any of Casebook's 3 triggers in the catalog, including New Case, New Intake Report and New Person. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Plentyone when something happens in Casebook?
Any of Plentyone's 20 actions, including Update contact, Update item, Update order and Update variation. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Plentyone to Casebook?
Plentyone has no triggers in the catalog today, so automations start in Casebook. If you need the other direction, ask: your agent reads Plentyone's API documentation and adds it.
Do I have to build a connector for Casebook or Plentyone?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Casebook and Plentyone without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.