Build it
What do you want Docparser and EOSL 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 Docparser and EOSL
Triggers and actions 2 triggers ยท 6 actions
Trigger
Parsed Document Data AvailableTriggers whenever a new Document is processed and parsed data is available.
- Parsed Table Row Available
Triggers whenever a new Document is processed and parsed table rows are available.
- Fetch Document From URL
Fetches 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).
- Upload Document
Uploads 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).
Action
Find part statusLook up end-of-support/end-of-life status by part number in the lookup table. Endpoint: GET /data/lookup.json
- Get part status
Get a one-line end-of-support/end-of-life status for a single part number, suitable for spreadsheet lookups. Endpoint: GET /cell/{part}.txt
- Get product family
Get full end-of-support/end-of-life detail for one product family by its slug. Endpoint: GET /api/v1/family/{slug}.json
- List product families
List every tracked product family with its end-of-support/end-of-life status. Endpoint: GET /api/v1/families.json
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