Integration
Connect Parseur to Linq
When New Document Export Failed fires in Parseur, your agent runs Add message to chat in Linq. 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 Parseur and Linq 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 Parseur can start in Linq
When New Document Export Failed in Parseur
then Add message to chat in Linq
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 Parseur and Linq
Triggers and actions 6 triggers · 21 actions
- New Document Export Failed
Triggered when Parseur fails to export a document to its destination.
- New Document Not Processed
Triggered when Parseur receives a document it cannot extract data from, so you can follow it up.
- New Document Processed
Triggered when Parseur finishes extracting data from a document, with the extracted fields.
- New Document Processed (With List Items)
Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).
- New Mailbox
Triggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
- New Table Field Processed
Triggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.
- Create Document
Sends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
- Create Document From File
Uploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
- Delete Document
Deletes a document from Parseur by its ID.
- Delete Mailbox
Deletes a Parseur mailbox and everything in it. This cannot be undone.
- Get Document
Returns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
- Get Mailbox
Returns one Parseur mailbox by its ID, with its email address, document counts and settings.
- List Documents
Returns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
- List Mailboxes
Returns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
- Reprocess Document
Sends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
- Update Mailbox
Updates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
- Add chat
Creates a new chat with one or more recipients and sends the initial message. If a chat already exists between the same sender and recipients, the message is sent into that chat.
- Add message to chat
Sends a message (text, media, link or experience card) to an existing Linq chat and returns the queued message.
- Add participant
Adds a new participant to an existing group chat. The addition is queued, and the new participant must use the same messaging service as the group.
- Add reaction
Adds or removes a reaction (tapback, custom emoji, or sticker) on an iMessage message.
- Find iMessage capability
Checks whether a phone number or email address can be reached over iMessage and returns the result.
- Get chat
Returns a Linq chat by its ID, including its display name, participants, group status and health status. An error occurs if the chat is not found.
- Get message
Returns one message by its ID, including its text and media parts, reactions, sender and delivery status.
- List chats
Returns the chats on your Linq account, optionally limited to one of your phone numbers or to chats with a given participant.
- List messages
Returns the messages in a Linq chat, including their text, media, reactions and delivery status.
- List phone numbers
Returns all phone numbers assigned to your Linq account, including each line's type, status and reputation.
- Update chat
Updates a group chat's display name and/or group icon. The change is queued and applied asynchronously.
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 Parseur
Parseur to ChartimagegeneratorEdge-rendered chart image API that converts Chart.js configurations into cached PNG/SVG images.
Parseur to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Parseur to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Parseur to StripeStripe is a payment processing platform for online businesses.
Parseur to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Parseur to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Linq
HubSpot to LinqHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LinqGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LinqGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LinqGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Parseur and Linq, answered
What can start an automation from Parseur?
Any of Parseur's 6 triggers in the catalog, including New Document Export Failed, New Document Not Processed, New Document Processed and New Document Processed (With List Items). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Linq when something happens in Parseur?
Any of Linq's 11 actions, including Update chat, Add chat, Add message to chat and Add participant. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Linq to Parseur?
Linq has no triggers in the catalog today, so automations start in Parseur. If you need the other direction, ask: your agent reads Linq's API documentation and adds it.
Do I have to build a connector for Parseur or Linq?
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 Parseur and Linq 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.