Integration
Connect Deskpro and Rotessa
When New Organization fires in Deskpro, your agent runs Create Customer in Rotessa, or New Customer in Rotessa to Add Message to Ticket in Deskpro. 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 Deskpro 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 Deskpro and Rotessa can do together
From Deskpro to Rotessa
When New Organization in Deskpro
then Create Customer in Rotessa
From Rotessa to Deskpro
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 Deskpro and Rotessa
Triggers and actions 9 triggers · 21 actions
- New Organization
Triggers when a new organization is created in Deskpro.
- New Person
Triggers when a new person is created in Deskpro.
- New Ticket
Triggers when a new ticket is created in Deskpro.
- New Ticket Reply
Triggers when an agent replies to a Deskpro ticket.
- Ticket Update
Triggers when a Deskpro ticket's status changes.
- Add Message to Ticket
Adds a reply or an internal note to an existing Deskpro ticket.
- Create Organization
Creates a new organization in Deskpro.
- Delete ticket
Deletes a ticket in Deskpro.
- Find Organization
Finds a Deskpro organization by name.
- Find Person
Finds a Deskpro person by primary email address.
- Find Ticket
Finds a Deskpro ticket by its reference code.
- Get organization
Returns a Deskpro organization by its ID, including its custom field values.
- Get person
Returns a single Deskpro person (user or agent) by ID, including emails, phone numbers, organization and custom field values.
- Get ticket
Returns a single Deskpro ticket by its ID, including its custom field values.
- Update person
Updates an existing person (contact) in Deskpro, changing only the details you fill in.
- Customer Change
Triggers when a Rotessa customer is added or updated.
- Declined Transaction
Triggers when a Rotessa payment is declined.
- New Customer
Triggers when a new customer is added in Rotessa.
- Transaction Approved
Triggers when a Rotessa payment is approved.
- Create Customer
Creates a new customer in Rotessa with their bank details.
- Create Transaction
Creates a one-time or recurring payment (transaction schedule) for a Rotessa customer.
- Create Transaction Schedule by Custom Identifier
Creates a one-time or recurring payment for the customer identified by your custom identifier.
- Delete Transaction Schedule
Deletes a transaction schedule so no further payments are processed.
- Get Customer
Returns one Rotessa customer by ID, including bank details, address and schedules.
- Get Transaction Schedule
Returns one transaction schedule and its payments.
- List Customers
Returns all customers in your Rotessa account.
- List Transactions
Returns payments processed in a date range, optionally filtered by status (Pending, Approved, Declined, Chargeback).
- Match a Customer
Finds the Rotessa customer that carries your custom identifier.
- Update Customer
Updates an existing Rotessa customer's contact or bank details.
- Update Transaction Schedule
Changes 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 Deskpro
Deskpro to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Deskpro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Deskpro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Deskpro to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Deskpro to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Deskpro to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Rotessa
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
Deskpro and Rotessa, answered
What can start an automation from Deskpro?
Any of Deskpro's 5 triggers in the catalog, including New Organization, New Person, New Ticket and New Ticket Reply. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Rotessa when something happens in Deskpro?
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 Deskpro?
Yes. When something happens in Rotessa, your agent can act in Deskpro too. This page covers both directions: Rotessa's triggers and Deskpro's actions are listed here as well.
Do I have to build a connector for Deskpro 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 Deskpro 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.