Build it
What do you want Airparser and SLF 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 Airparser and SLF
Triggers and actions 1 trigger · 10 actions
Trigger
Document ParsedTriggers when Airparser finishes parsing a document in the chosen inbox, giving you the extracted data.
Action
Create an InboxCreates a new Airparser inbox that documents can be sent to for parsing.
Action
Create or Update Extraction SchemaSets which fields Airparser should pull out of documents sent to an inbox, replacing whatever schema was there before.
Action
Delete an InboxDeletes an Airparser inbox and the documents stored in it.
Action
Extract Data From a DocumentSends a document to an Airparser inbox, waits for it to be parsed, and returns the extracted data.
Action
Extract Data From a Document (Async)Sends a document to an Airparser inbox and returns straight away without waiting for parsing. Use the Document Parsed trigger or Get Document to pick up the result.
Action
Get a DocumentReturns a parsed Airparser document, including the data extracted from it.
Action
Get an InboxReturns one Airparser inbox with its settings, its email address prefix and its current extraction schema.
Action
List DocumentsLists the documents in an Airparser inbox, with the data extracted from each one.
Action
List InboxesLists all the Airparser inboxes in the connected account.
Action
Get Stadt-Land-Fluss dataFetch the full German Stadt-Land-Fluss (city/country/river word-game) reference dataset via GET https://slftool.github.io/data.json. Static, unauthenticated, single-request JSON blob keyed by letter, each letter holding arrays for stadt (city), land (country), fluss (river), name, beruf (profession), tier (animal), and marke (brand). No query parameters — the vendor exposes no filtering or search; the whole dataset is returned every call and any per-letter/per-category lookup must be done client-side on the response.
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