Integration
Connect Parseur to ManyRequests
When New Document Export Failed fires in Parseur, your agent runs Add invoice in ManyRequests. 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 ManyRequests 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 ManyRequests
When New Document Export Failed in Parseur
then Add invoice in ManyRequests
When New Document Not Processed in Parseur
then Create Client in ManyRequests
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 ManyRequests
Triggers and actions 6 triggers · 37 actions
Trigger
New Document Export FailedTriggered when Parseur fails to export a document to its destination.
Trigger
New Document Not ProcessedTriggered when Parseur receives a document it cannot extract data from, so you can follow it up.
Trigger
New Document ProcessedTriggered when Parseur finishes extracting data from a document, with the extracted fields.
Trigger
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).
Trigger
New MailboxTriggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
Trigger
New Table Field ProcessedTriggers 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.
Action
Create DocumentSends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Create Document From FileUploads 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.
Action
Delete DocumentDeletes a document from Parseur by its ID.
Action
Delete MailboxDeletes a Parseur mailbox and everything in it. This cannot be undone.
Action
Get DocumentReturns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
Action
Get MailboxReturns one Parseur mailbox by its ID, with its email address, document counts and settings.
Action
List DocumentsReturns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
Action
List MailboxesReturns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
Action
Reprocess DocumentSends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
Action
Update MailboxUpdates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
Action
Add invoiceAdds a new invoice for a client from catalog services, pricing variations or custom line items, and returns the new invoice's id. The invoice is emailed to the client unless it is created as a draft.
Action
Add organizationCreates a new organization in your ManyRequests portal along with its owner client user. Returns the organization that was added.
Action
Add organization memberAdds a member to an organization, creating a new client user if no user with that email exists yet.
Action
Add subscription to organizationAdds a recurring service subscription to a client organization and returns the new subscription.
Action
Add time entryLogs time worked on a request for a team member, from a start time to an end time.
Action
Cancel Client SubscriptionCancels an active recurring service subscription belonging to a client organization.
Action
Create ClientCreates a client user in a ManyRequests organization. If a user with the email already exists, they are added to the organization.
Action
Create CommentAdds a comment to a request, posted as the chosen user, optionally internal-only or scheduled for later delivery.
Action
Create organization brandCreates a new brand within an organization.
Action
Create RequestCreates a new service request for a client under one of your services, with an optional description, priority, status, due date, brand, assignees and tags.
Action
Delete clientDeletes a client and removes them from their organization. A client who is the sole owner of an organization with active subscriptions cannot be deleted.
Action
Delete organizationDeletes an organization and all of its members from your ManyRequests portal.
Action
Delete requestDeletes a request in ManyRequests.
Action
Find Comments for RequestReturns the comments on a ManyRequests request, optionally limited to internal or non-internal comments.
Action
Find OrganizationFinds organizations whose name, owner name or owner email matches the search text, optionally narrowed by tags or subscription status.
Action
Find RequestReturns the service requests that match your search text or filters, such as status, priority, client, organization, assignee or request number.
Action
Get clientReturns a single client by ID, including their name, email and organization.
Action
Get invoiceReturns a single invoice with its status, number, notes, payment details and dates, optionally with its line items, taxes, client, coupon and payment gateway.
Action
Get organizationReturns a single organization by its ID, with its name, logo and dates, plus any related records you ask to include. An error occurs if the organization is not found.
Action
Get requestReturns a single service request by its ID or slug, with optional related records such as status, client, service, tags and form fields.
Action
List clientsReturns the clients in your ManyRequests portal, with optional search, organization filter and sorting.
Action
List servicesReturns the services offered in your ManyRequests portal, optionally filtered by search text, type, allocation or sale status.
Action
List team membersReturns the portal admins, admins and team members in your ManyRequests portal, optionally filtered by email or role.
Action
Update clientUpdates a client's name and/or email address.
Action
Update organizationUpdates the name of an existing organization and returns the updated organization.
Action
Update RequestUpdates an existing request's title, description, priority, status, due date, brand, assignees, tags or form fields.
Action
Update Request StatusMoves a ManyRequests request to a different status.
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 ManyRequests
HubSpot to ManyRequestsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ManyRequestsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ManyRequestsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ManyRequestsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ManyRequestsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ManyRequestsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Parseur and ManyRequests, 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 ManyRequests when something happens in Parseur?
Any of ManyRequests's 27 actions, including Create Client, Create Comment, Create organization brand and Create Request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ManyRequests to Parseur?
ManyRequests has no triggers in the catalog today, so automations start in Parseur. If you need the other direction, ask: your agent reads ManyRequests's API documentation and adds it.
Do I have to build a connector for Parseur or ManyRequests?
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 ManyRequests 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.