Build it
What do you want Docparser and CodeCogs 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 CodeCogs
Triggers and actions 2 triggers ยท 3 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
Render LaTeX equationRenders a LaTeX equation to an image or JSON payload via GET https://latex.codecogs.com/{type}.{format}?{LaTeX}, where type is png|gif|svg|emf|pdf, format is image|json|javascript|download, and the query is the raw LaTeX markup (may include \dpi{#}, \bg{#}, \fg{#}, and size directives like \small/\large). Returns the rendered image bytes (image formats) or a JSON object with base64-encoded equation details (json format). No authentication required.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.