Integration
Connect Clientary and Rotessa
When New Expense fires in Clientary, your agent runs Create Customer in Rotessa, or New Customer in Rotessa to Add contact in Clientary. 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 Clientary and Rotessa 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Clientary and Rotessa can do together
From Clientary to Rotessa
When New Expense in Clientary
then Create Customer in Rotessa
When New Invoice in Clientary
then Update Customer in Rotessa
From Rotessa to Clientary
When New Customer in Rotessa
then Add contact in Clientary
When Customer Change in Rotessa
then Create Invoice in Clientary
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 Clientary and Rotessa
Triggers and actions 7 triggers · 25 actions
Trigger
New ExpenseTriggers when a new expense is recorded in your Clientary account during the current fiscal year.
Trigger
New InvoiceTriggers when a new invoice is created in Clientary, optionally limited to invoices in a given status or matching a search.
Trigger
New StaffTriggers when a new staff user is added to your Clientary account.
Action
Add commentPosts a comment on an invoice, estimate, project, task, proposal or contract and notifies the people involved.
Action
Add contactCreates a new contact (an individual person) under an existing Clientary client.
Action
Add contractCreates a contract for a client in Clientary, optionally starting from a contract template, with its sections and signers.
Action
Add proposalCreates a proposal for a client in Clientary, optionally starting from a proposal template, with its sections and signers.
Action
Add retainerCreates a retainer for a client in Clientary: an up-front payment request kept apart from ordinary invoices.
Action
ClientCreates a new client in Clientary with its name, address, tax id, website and description.
Action
Create EstimateCreates an estimate in Clientary, optionally for a client, with its dates, taxes, notes and line items.
Action
Create InvoiceCreates an invoice in Clientary, optionally for a client, with dates, currency, taxes, notes and line items.
Action
Create LeadCreates a new lead (a prospective client) in Clientary.
Action
Create TaskCreates a new task (a to-do item) in Clientary, optionally on a project and assigned to a staff member.
Action
ExpenseCreates a new expense in Clientary, optionally assigned to a client or project.
Action
Get clientReturns a single Clientary client by its ID, including its contact and address details.
Action
List commentsReturns the comments on one Clientary invoice, estimate, project, task, proposal or contract, newest first.
Action
Update contractUpdates an existing Clientary contract: its subject, date, client, status, signers or sections. Only a draft contract can be changed; void and reopen a sent contract first.
Trigger
Customer ChangeTriggers when a Rotessa customer is added or updated.
Trigger
Declined TransactionTriggers when a Rotessa payment is declined.
Trigger
New CustomerTriggers when a new customer is added in Rotessa.
Trigger
Transaction ApprovedTriggers when a Rotessa payment is approved.
Action
Create CustomerCreates a new customer in Rotessa with their bank details.
Action
Create TransactionCreates a one-time or recurring payment (transaction schedule) for a Rotessa customer.
Action
Create Transaction Schedule by Custom IdentifierCreates a one-time or recurring payment for the customer identified by your custom identifier.
Action
Delete Transaction ScheduleDeletes a transaction schedule so no further payments are processed.
Action
Get CustomerReturns one Rotessa customer by ID, including bank details, address and schedules.
Action
Get Transaction ScheduleReturns one transaction schedule and its payments.
Action
List CustomersReturns all customers in your Rotessa account.
Action
List TransactionsReturns payments processed in a date range, optionally filtered by status (Pending, Approved, Declined, Chargeback).
Action
Match a CustomerFinds the Rotessa customer that carries your custom identifier.
Action
Update CustomerUpdates an existing Rotessa customer's contact or bank details.
Action
Update Transaction ScheduleChanges the amount or comment of an existing transaction schedule.
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 Clientary
Clientary to ViaCepViaCep is a Brazilian postal code (CEP) lookup service.
Clientary to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clientary to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clientary to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clientary to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Clientary to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Rotessa
HubSpot to RotessaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to RotessaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to RotessaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RotessaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to RotessaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RotessaMailchimp marketing automation and email platform.
Questions
Clientary and Rotessa, answered
What can start an automation from Clientary?
Any of Clientary's 3 triggers in the catalog, including New Expense, New Invoice and New Staff. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Rotessa when something happens in Clientary?
Any of Rotessa's 11 actions, including Create Customer, Create Transaction, Create Transaction Schedule by Custom Identifier and Update Customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Rotessa to Clientary?
Yes. When something happens in Rotessa, your agent can act in Clientary too. This page covers both directions: Rotessa's triggers and Clientary's actions are listed here as well.
Do I have to build a connector for Clientary or Rotessa?
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 Clientary and Rotessa 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.