Integration
Connect Loyverse to Ashby
When Customer Update fires in Loyverse, your agent runs Create Candidate Note in Ashby. 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 Loyverse and Ashby 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 Loyverse can start in Ashby
When Customer Update in Loyverse
then Create Candidate Note in Ashby
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 Loyverse and Ashby
Triggers and actions 4 triggers · 62 actions
- Customer Update
Triggers when a customer is updated.
- Inventory Update
Triggers when a stock updates.
- Items Update
Triggers when an item is updated.
- Receipts Update
Triggers when a receipt gets created or updated.
- Create or Update Category
Creates or Updates a single category.
- Create or Update Discount
Creates or Updates a single discount.
- Create or Update Modifier
Creates or Updates a modifier.
- Create or Update POS Device
Creates or Updates a single POS device.
- Create or Update Receipts
Creates a receipt
- Create or Update Single Customer
Creates or Updates a Single Customer.
- Create or Update Single Item
- Create or Update Supplier
Creates or Updates a single supplier.
- Create or Update Tax
Creates or Updates a tax.
- Create Refund Receipt
Creates 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.
- Delete Singe Item
Deletes a single item.
- Delete Single Category
Deletes a single category.
- Delete Single Customer
Deletes a single customer.
- Delete Single Discount
Deletes a single discount.
- Delete Single Modifier
Deletes a single Modifier.
- Delete Single POS Device
Deletes a single POS Device.
- Delete Single Supplier
Deletes a single supplier.
- Delete Single Tax
Deletes a single tax.
- Delete Single Variant
Deletes a single variant.
- Get List of Categories
Get list of all categories.
- Get List of Customers
Get list of Customers
- Get List of Discounts
Returns discounts, most recently created first.
- Get List of Employees
Gets a list of employees.
- Get List of Items
Get list of items
- Get List of Payment Types
Get list of Payment Types
- Get List of POS Devices
The list of pos devices is sorted by created_at property in descending order. The most recent pos devices appear first
- Get List of Stores
Get list of stores
- Get List of Suppliers
Gets a list of suppliers.
- Get List of Taxes
Get list of taxes
- Get List of Variants
Get lists of item variants.
- Get Merchant Information
Returns the business profile of the connected Loyverse merchant account.
- Get Single Category
Get Single Category.
- Get Single Customer
Get Single Customer
- Get Single Discount
Gets a single discount.
- Get Single Employee
Gets a single employee.
- Get Single Item
Get single item
- Get Single Modifier
Gets a single modifier.
- Get Single Payment Type
Fetches a payment type by ID. An error occurs if the payment type is not found.
- Get Single POS Device
Fetches a POS device by ID. An error occurs if the POS device is not found.
- Get Single Receipt
Get a single Receipt.
- Get Single Store
Get Single Store
- Get Single Supplier
Fetches a supplier by ID. An error occurs if the supplier is not found.
- Get Single Tax
Gets a single tax.
- Get Single Variant
Gets single item variant.
- Update Inventory Levels for Items
Batch updates Inventory Levels for Item Variants.
- Add candidate tag
Adds an existing tag to a candidate in Ashby and returns the updated candidate.
- Add job
Creates a new job in Ashby with a title, department/team and location, optionally applying a job template, interview plan, employment type and brand.
- Add offer
Creates an offer for a candidate's application in Ashby by submitting the offer form for an offer process that has already been started.
- Change Job Consideration Stage
Moves a candidate's application (their consideration for a job) to a different interview stage, optionally with an archive reason and rejection email when archiving.
- Consider Candidate for Job
Considers a candidate for a job in Ashby by creating a new application, optionally placing it in a specific interview plan and stage with a source and credited user.
- Create Candidate
Creates a new candidate in Ashby with their name, contact details, social profiles, location and source.
- Create Candidate Note
Adds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.
- Find Candidate
Returns up to 100 candidates whose email address and/or name match the values you supply.
- Find Job
Returns up to 100 jobs whose title or requisition ID matches the text you search for.
- Find Job Consideration
Returns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.
- Find Opening
Returns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.
- Get candidate
Returns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.
- List departments
Returns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.
- List locations
Returns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.
- Update Candidate
Updates an existing candidate's name, contact details, social links, source, credited user and location in Ashby. Fields left blank are not changed.
- Update job
Updates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.
- Update Opening
Updates an existing opening in Ashby, such as its identifier, description, department, target dates, backfill flag or employment type. Returns the updated opening.
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 Loyverse
Loyverse to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Loyverse to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Loyverse to MailchimpMailchimp marketing automation and email platform.
Loyverse to StripeStripe is a payment processing platform for online businesses.
Loyverse to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Loyverse to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Ashby
HubSpot to AshbyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to AshbyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to AshbyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AshbyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Loyverse and Ashby, answered
What can start an automation from Loyverse?
Any of Loyverse's 4 triggers in the catalog, including Customer Update, Inventory Update, Items Update and Receipts Update. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ashby when something happens in Loyverse?
Any of Ashby's 17 actions, including Create Candidate, Create Candidate Note, Update Candidate and Update job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ashby to Loyverse?
Ashby has no triggers in the catalog today, so automations start in Loyverse. If you need the other direction, ask: your agent reads Ashby's API documentation and adds it.
Do I have to build a connector for Loyverse or Ashby?
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 Loyverse and Ashby 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.