Build it
What do you want iDigBio and NEXT 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 NEXT
Triggers and actions 1 trigger ยท 21 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
Add RecordCreate a record (feedback/insight item) in NEXT. POST /records
- Add Tag
Create a tag. POST /tags
- Create Account
Creates an account in NEXT
- Create Highlight
Creates a highlight in NEXT
- Create Recording
Creates a recording in NEXT
- Delete Record
Delete a record. DELETE /records/{id}
- Delete Tag
Delete a tag. DELETE /tags/{id}
- Find Account
Find an account in NEXT
- Find Records by Relevance
Search records by relevance/query. GET /search-records
- Get Project
Retrieve a project. GET /projects/{id}
- Get Record
Retrieve a record by ID. GET /records/{id}
- Get Tag
Retrieve a tag by ID. GET /tags/{id}
- List Tags
List all tags. GET /tags
- Update Record
Update an existing record. PUT /records/{id}
- Update Tag
Update a tag. PUT /tags/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews