Integration
Connect TestLocally to Docparser
When something happens in TestLocally, your agent does the next thing in Docparser. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want TestLocally and Docparser 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 TestLocally and Docparser
Triggers and actions 3 triggers ยท 6 actions
Trigger
New TestTriggers when a new test has been requested.
- Find Tests
Finds recent Test Results
- Get Random Locations
Returns a set of 1-9 random Location names
- Get Test Results
Gets the Test Result details
- Request New Test
Request a new screenshot from a set of locations
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).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.