Integration
Connect Casebook to Temsor
When New Case fires in Casebook, your agent runs Verify email in Temsor. 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 Temsor 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 Temsor
When New Case in Casebook
then Verify email in Temsor
When New Intake Report in Casebook
then Close promise in Temsor
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 Temsor
Triggers and actions 3 triggers · 25 actions
Trigger
New CaseTriggers when a new case is created in Casebook.
Trigger
New Intake ReportTriggers when a new intake report is created in Casebook.
Trigger
New PersonTriggers when a new person is created in Casebook.
Action
Add a Person to a CaseAdds a person to a Casebook case.
Action
Create a CaseCreates a new case in Casebook with a name, description and case type.
Action
Create an Intake ReportCreates a new intake report in Casebook with a name, narrative and report type.
Action
Create a NoteCreates a note in Casebook, optionally attached to a person, case or other record.
Action
Create a PersonCreates a new person in Casebook with their name and basic demographics.
Action
Create a ProviderCreates a new provider in Casebook with a name and contact details.
Action
Delete a PersonDeletes a person in Casebook. The record is hidden from view, not permanently purged.
Action
Find PeopleFinds Casebook people by first name, last name or date of birth and returns the first match.
Action
Get a CaseReturns one Casebook case by ID, including its name and description.
Action
Get an Intake ReportReturns one Casebook intake report by ID, including its name, narrative and when it was reported.
Action
Get a PersonReturns one Casebook person by ID, including name, date of birth and other demographics.
Action
Get a ProviderReturns one Casebook provider by ID, including its name, email and phone number.
Action
Update a CaseUpdates a Casebook case's name, description or goals. Only the fields you fill in are changed.
Action
Update a PersonUpdates a Casebook person's name or demographics. Only the fields you fill in are changed.
Action
Close promiseMarks an open call promise as kept or broken, with an optional short note, and returns the updated promise.
Action
Find calls by querySearches the call archive and returns the calls, call promises and extracted facts that match a text query, optionally narrowed by promise status, extension, competitor, date range or the extension a promise got stuck at.
Action
Get callReturns one call by its id, including its transfer path, handoff graph and count of open promises.
Action
List callsReturns the most recent calls in your Temsor call archive, with each call's direction, trunk, summary, transfer path and open promise count.
Action
List personsReturns the people seen in your call history — callers with their phones and names, and extensions seen on transfers — optionally filtered by call, kind or search text.
Action
List promisesReturns the call promises tracked for agent handoff, filtered by status (open by default), each with its caller, promise text, transfer path and where it got stuck.
Action
Redact textErases a caller's personal data from the Temsor call index — a promise, call, person, fact or utterance by id, or everything linked to a caller's phone number — by anonymizing or deleting it, and records an audit entry.
Action
Validate IBANValidates an IBAN from any of 70+ countries, checking its checksum, country length and account structure, and returns the bank and branch codes plus a corrected suggestion when only the check digits are wrong.
Action
Validate phone numberValidates a phone number and returns it in standard international (E.164) and national form, with its country and line type.
Action
Validate Turkish IDValidates a Turkish identifier — national ID (TCKN), tax number (VKN), IBAN, licence plate, IMEI, barcode, KEP address, MERSİS number, postal code or ISBN — detecting the type automatically when you don't specify it, and returns whether it is valid plus resolved details.
Action
Verify emailChecks an email address: its syntax, whether the domain can receive mail, whether it is disposable or a role account, and suggests a correction for common domain typos.
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 Temsor
HubSpot to TemsorHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TemsorSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TemsorSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TemsorGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TemsorGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TemsorGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Casebook and Temsor, 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 Temsor when something happens in Casebook?
Any of Temsor's 11 actions, including Close promise, Find calls by query, Get call and List calls. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Temsor to Casebook?
Temsor has no triggers in the catalog today, so automations start in Casebook. If you need the other direction, ask: your agent reads Temsor's API documentation and adds it.
Do I have to build a connector for Casebook or Temsor?
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 Temsor 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.