Integration
Connect Biyo POS and Docparser
When New Category fires in Biyo POS, your agent runs Upload Document in Docparser, or Parsed Document Data Available in Docparser to Create Terminal in Biyo POS. 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 Biyo POS and Docparser to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Biyo POS and Docparser can do together
From Biyo POS to Docparser
When New Category in Biyo POS
then Upload Document in Docparser
When New Product in Biyo POS
then Fetch Document From URL in Docparser
From Docparser to Biyo POS
When Parsed Document Data Available in Docparser
then Create Terminal in Biyo POS
When Parsed Table Row Available in Docparser
then Find Product in Biyo POS
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 Biyo POS and Docparser
Triggers and actions 7 triggers · 7 actions
Trigger
New CategoryTriggers when a new category is added to your Biyo POS account.
Trigger
New ProductTriggers when a new active product is added in Biyo POS.
Trigger
New StoreTriggers when a new store is added to your Biyo POS account.
Trigger
New Tax RateTriggers when a new tax rate is added to your Biyo POS account.
Trigger
New TerminalTriggers when a new POS terminal (register or kiosk) is added to your Biyo POS account.
Action
Create TerminalRegisters a new POS terminal in one of your Biyo stores and returns the created terminal.
Action
Find ProductFinds active products whose name contains the search text or whose barcode matches it exactly.
Action
Find StoreFinds a store (location) on your Biyo account by its name.
Action
Find Tax RateFinds a tax rate in your Biyo POS account by its name and returns its id and percentage.
Action
Find TerminalFinds a POS terminal (register or kiosk) by its name and returns its details.
Trigger
Parsed Document Data AvailableTriggers whenever a new Document is processed and parsed data is available.
Trigger
Parsed Table Row AvailableTriggers whenever a new Document is processed and parsed table rows are available.
Action
Fetch Document From URLFetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Upload DocumentUploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
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 Biyo POS
Biyo POS to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Biyo POS to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Biyo POS to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Biyo POS to Google SheetsGoogle Sheets
Biyo POS to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Biyo POS to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Docparser
ActiveCampaign to DocparserActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to DocparserOrganize anything with Airtable, a modern database created for everyone.
Asana to DocparserAsana is a collaborative information manager for workspace.
ClickUp to DocparserClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to DocparserDiscord is an all-in-one voice and text chat for gamers.
Brevo to DocparserBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
Biyo POS and Docparser, answered
What can start an automation from Biyo POS?
Any of Biyo POS's 5 triggers in the catalog, including New Category, New Product, New Store and New Tax Rate. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Docparser when something happens in Biyo POS?
Any of Docparser's 2 actions, including Upload Document and Fetch Document From URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Docparser to Biyo POS?
Yes. When something happens in Docparser, your agent can act in Biyo POS too. This page covers both directions: Docparser's triggers and Biyo POS's actions are listed here as well.
Do I have to build a connector for Biyo POS or Docparser?
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.
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.