Build it
What do you want Parseur and ITIS to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Parseur and ITIS
Triggers and actions 6 triggers · 23 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
Convert LSID to TSNGet the TSN for a given LSID (Life Science Identifier).
Action
Convert TSN to LSIDGet the LSID (Life Science Identifier) for a given TSN.
Action
Find taxon by common nameSearch ITIS for taxa matching a common (vernacular) name.
Action
Find taxon by scientific nameSearch ITIS for taxa matching a scientific name.
Action
Find taxon by search termSearch ITIS across scientific and common names for any matching term.
Action
Get accepted namesGet the currently accepted scientific name(s) for a given TSN, when the queried TSN is not itself accepted.
Action
Get common namesGet the common (vernacular) names associated with a given TSN.
Action
Get full hierarchyGet the complete taxonomic hierarchy (ancestors and descendants) for a given TSN.
Action
Get full recordGet the complete taxonomic record for a given TSN (taxonomic serial number).
Action
Get hierarchy downGet the taxonomic hierarchy below (children of) a given TSN.
Action
Get hierarchy upGet the taxonomic hierarchy above (ancestors of) a given TSN.
Action
Get parent taxonGet the parent TSN for a given TSN.
Action
Get synonym namesGet the synonym scientific names associated with a given TSN.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.