Integration
Connect iDigBio to Universities List
When something happens in iDigBio, your agent does the next thing in Universities List. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want iDigBio and Universities List 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 iDigBio and Universities List
Triggers and actions 1 trigger · 7 actions
Trigger
New recordPolls for specimen records newly indexed into iDigBio matching a saved search query, sorted by modified/index date. GET /v2/search/records/ sorted on datemodified.
- Find media records
Search iDigBio media records (images/media associated with specimens) matching a query. GET/POST /v2/search/media/ using the iDigBio Query Format (mq/rq parameters).
- Find records
Search iDigBio specimen records matching a query. GET/POST /v2/search/records/ using the iDigBio Query Format (rq parameter).
- Find recordsets
Search iDigBio recordsets (collections/datasets contributed by publishers) matching a query. GET/POST /v2/search/recordsets/ using the iDigBio Query Format (rsq parameter).
- Get media record
Retrieve a single iDigBio media record by its UUID. GET /v2/view/mediarecords/{uuid}.
- Get record
Retrieve a single iDigBio specimen record by its UUID. GET /v2/view/records/{uuid}.
- Get recordset
Retrieve a single iDigBio recordset (dataset) by its UUID. GET /v2/view/recordsets/{uuid}.
Action
Find universitiesSearch the University Domains List hosted API (http://universities.hipolabs.com/search) for universities matching an optional name and/or country. Query params: name (substring match), country (exact country name, e.g. "Turkiye"). No auth required. Returns an array of {name, country, alpha_two_code, state-province, domains[], web_pages[]}. This is the only real endpoint the vendor exposes — the rest of the project is a static JSON data file, not an API.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.