Integration
Connect Wachete to Crossref Metadata Search
When something happens in Wachete, your agent does the next thing in Crossref Metadata Search. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Wachete and Crossref Metadata Search 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 Wachete and Crossref Metadata Search
Triggers and actions 2 triggers · 13 actions
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
Action
Find funders by querySearch the Crossref Funder Registry for funding organizations matching a free-text query. GET /funders
- Find works by query
Search Crossref's bibliographic metadata for works (articles, books, conference papers, etc.) matching a free-text query, with optional filters and sorting. GET /works
- Get funder
Retrieve metadata for a funding organization and its suborganizations by funder ID. GET /funders/{funder_id}
- Get journal
Retrieve information about a journal by its ISSN. GET /journals/{issn}
- Get member
Retrieve metadata for a Crossref member (publisher) by member ID. GET /members/{member_id}
- Get work by DOI
Retrieve full Crossref metadata for a single work given its DOI. GET /works/{doi}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.