Build it
What do you want Docparser and PayCrunch 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 PayCrunch
Triggers and actions 2 triggers ยท 7 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
Get jobGet full wage and detail data for one occupation by its slug. Endpoint: GET /jobs/{slug}.json
- Get SOC code wage data
Get the state-by-state wage table for one Standard Occupational Classification (SOC) code. Endpoint: GET /soc/{code}.json
- List best-paying states by occupation
List the best-paying state for each occupation. Endpoint: GET /states.json
- List jobs
List every occupation covered by PayCrunch, with summary wage data. Endpoint: GET /jobs.json
- List state wages
List wage figures by state for every occupation. Endpoint: GET /state-wages.json
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.