Integration
Connect Áskell and Loyverse
When New Customer fires in Áskell, your agent runs Create or Update Single Customer in Loyverse, or Customer Update in Loyverse to Create Customer in Áskell. 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 Áskell and Loyverse 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 Áskell and Loyverse can do together
From Áskell to Loyverse
When New Customer in Áskell
then Create or Update Single Customer in Loyverse
When New Subscription in Áskell
then Create or Update Single Item in Loyverse
From Loyverse to Áskell
When Customer Update in Loyverse
then Create Customer in Áskell
When Inventory Update in Loyverse
then Update customer in Áskell
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 Áskell and Loyverse
Triggers and actions 6 triggers · 63 actions
Trigger
New CustomerTriggers when a new customer is created in Áskell.
Trigger
New SubscriptionTriggers when a new subscription is created in Áskell.
Action
Activate SubscriptionRe-activates a cancelled Áskell subscription, as long as its latest billing period has not passed.
Action
Add paymentCreates a one-off payment for an Áskell customer. The payment starts as pending and settles or fails asynchronously.
Action
Add subscriptionAdds a subscription to an existing customer on a plan, charging the first period with the customer's payment method unless the plan has a trial.
Action
Cancel SubscriptionCancels an active Áskell subscription and returns its new state.
Action
Create CustomerCreates a customer in Áskell under a reference you choose, so you can look the customer up later.
Action
Delete customerDeletes a customer from Áskell by their customer reference.
Action
Get CustomerReturns one Áskell customer, looked up by the customer reference you assigned when creating it.
Action
Get paymentReturns a single Áskell payment in detail, including its amount, state, refunded amount and transactions.
Action
Get planReturns a single Áskell plan variant by its id, including its name, price, billing interval and payment processor.
Action
Get SubscriptionReturns one Áskell subscription by its id, including its status, customer and dates.
Action
List customersReturns all customers in your Áskell account, with their contact details and payment methods.
Action
List paymentsReturns all payments in your Áskell account, with amount, state, refunds and their transactions.
Action
List plansReturns every plan variant in your Áskell account, each with its name, price, currency and billing interval.
Action
List subscriptionsReturns all subscriptions in your Áskell account, with each subscription's plan, customer and status.
Action
List transactionsReturns the transactions on your Áskell account. You can filter them by state, subscription, payment or date range.
Action
Refund paymentRefunds a settled Áskell payment, in full or for a partial amount.
Action
Update customerUpdates an existing Áskell customer's name, email or phone. Fields left blank are not changed.
Action
Update subscriptionUpdates an Áskell subscription's plan, amount, discount or internal description.
Trigger
Customer UpdateTriggers when a customer is updated.
Trigger
Inventory UpdateTriggers when a stock updates.
Trigger
Items UpdateTriggers when an item is updated.
Trigger
Receipts UpdateTriggers when a receipt gets created or updated.
Action
Create or Update CategoryCreates or Updates a single category.
Action
Create or Update DiscountCreates or Updates a single discount.
Action
Create or Update ModifierCreates or Updates a modifier.
Action
Create or Update POS DeviceCreates or Updates a single POS device.
Action
Create or Update ReceiptsCreates a receipt
Action
Create or Update Single CustomerCreates or Updates a Single Customer.
Action
Create or Update Single ItemAction
Create or Update SupplierCreates or Updates a single supplier.
Action
Create or Update TaxCreates or Updates a tax.
Action
Create Refund ReceiptCreates a refund receipt. When using the refund API you should take into account these notes: - At the moment refund API allows creating a refund only for sales receipts which are paid by a single payment. For any attempt to make a refund for a sales receipt that has more than one payment Loyverse API will respond with an error. - Refund API doesn't support a refund of receipts paid by integrated payments using Loyverse POS app (e.g. iZettle, Sumup, etc.). For this purpose please use Loyverse POS app. - If a refund is created successfully, it will cause a restock of items specified in a refund receipt.
Action
Delete Singe ItemDeletes a single item.
Action
Delete Single CategoryDeletes a single category.
Action
Delete Single CustomerDeletes a single customer.
Action
Delete Single DiscountDeletes a single discount.
Action
Delete Single ModifierDeletes a single Modifier.
Action
Delete Single POS DeviceDeletes a single POS Device.
Action
Delete Single SupplierDeletes a single supplier.
Action
Delete Single TaxDeletes a single tax.
Action
Delete Single VariantDeletes a single variant.
Action
Get List of CategoriesGet list of all categories.
Action
Get List of CustomersGet list of Customers
Action
Get List of DiscountsReturns discounts, most recently created first.
Action
Get List of EmployeesGets a list of employees.
Action
Get List of ItemsGet list of items
Action
Get List of Payment TypesGet list of Payment Types
Action
Get List of POS DevicesThe list of pos devices is sorted by created_at property in descending order. The most recent pos devices appear first
Action
Get List of StoresGet list of stores
Action
Get List of SuppliersGets a list of suppliers.
Action
Get List of TaxesGet list of taxes
Action
Get List of VariantsGet lists of item variants.
Action
Get Merchant InformationReturns the business profile of the connected Loyverse merchant account.
Action
Get Single CategoryGet Single Category.
Action
Get Single CustomerGet Single Customer
Action
Get Single DiscountGets a single discount.
Action
Get Single EmployeeGets a single employee.
Action
Get Single ItemGet single item
Action
Get Single ModifierGets a single modifier.
Action
Get Single Payment TypeFetches a payment type by ID. An error occurs if the payment type is not found.
Action
Get Single POS DeviceFetches a POS device by ID. An error occurs if the POS device is not found.
Action
Get Single ReceiptGet a single Receipt.
Action
Get Single StoreGet Single Store
Action
Get Single SupplierFetches a supplier by ID. An error occurs if the supplier is not found.
Action
Get Single TaxGets a single tax.
Action
Get Single VariantGets single item variant.
Action
Update Inventory Levels for ItemsBatch updates Inventory Levels for Item Variants.
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 Áskell
Áskell to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Áskell to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Áskell to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Áskell to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Áskell to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Áskell to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Loyverse
Erpnext to LoyverseOpen-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.
HubSpot to LoyverseHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LoyverseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LoyverseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LoyverseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LoyverseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Áskell and Loyverse, answered
What can start an automation from Áskell?
Any of Áskell's 2 triggers in the catalog, including New Customer and New Subscription. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Loyverse when something happens in Áskell?
Any of Loyverse's 45 actions, including Create or Update Category, Create or Update Discount, Create or Update Modifier and Create or Update POS Device. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Loyverse to Áskell?
Yes. When something happens in Loyverse, your agent can act in Áskell too. This page covers both directions: Loyverse's triggers and Áskell's actions are listed here as well.
Do I have to build a connector for Áskell or Loyverse?
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 Áskell and Loyverse 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.