Build it
What do you want Mapulus 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 Mapulus and PayCrunch
Triggers and actions 2 triggers ยท 10 actions
Trigger
New LocationTriggers when a new location is added in Mapulus.
- New Map
Triggers when a new map is created in Mapulus.
- Create Location
Adds a location pin to a layer on a Mapulus map, from an address or from coordinates.
- Delete Location
Removes a location pin from a Mapulus map.
- Find Location
Returns Mapulus locations, optionally limited to one map or to the location with a given external ID.
- Find Map
Returns the maps in your Mapulus account, so you can pick the one to add locations to.
- Update Location
Updates a location pin in Mapulus. Only the fields you supply are changed.
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.