Integration
Connect Ticketeer to Crossref Metadata Search
When something happens in Ticketeer, 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 Ticketeer 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 Ticketeer and Crossref Metadata Search
Triggers and actions 5 triggers ยท 27 actions
Trigger
Comment AddedTriggers when a comment is added in any task in the selected board.
Trigger
New boardFires when a new board is created. Polls GET /v1/boards.
Trigger
Task AssignedTriggers when a task is is assigned to a user in the selected board.
Trigger
Task CreatedTriggers when a task is created in the selected board.
Trigger
Task MovedTriggers when a task is moved both within a column and between columns in the selected board.
Action
Add boardCreate a new board. Endpoint: POST /v1/boards.
Action
Add commentAdd a comment to a task. Endpoint: POST /v1/boards/{boardID}/tasks/{taskID}/comments.
Action
Add tagCreate a new tag on a board. Endpoint: POST /v1/boards/{boardID}/tags.
Action
Create TaskCreates a task in the specified column of the specified board
Action
Delete boardDelete a board. Endpoint: DELETE /v1/boards/{boardID}.
Action
Delete tagDelete a tag from a board. Endpoint: DELETE /v1/boards/{boardID}/tags/{tagID}.
Action
Delete taskDelete a task. Endpoint: DELETE /v1/boards/{boardID}/tasks/{taskID}.
Action
Get boardRetrieve a single board by id. Endpoint: GET /v1/boards/{boardID}.
Action
Get columnRetrieve a single column on a board. Endpoint: GET /v1/boards/{boardID}/columns/{columnID}.
Action
Get taskRetrieve a single task by id. Endpoint: GET /v1/boards/{boardID}/tasks/{taskID}.
Action
List boardsList the boards visible to the connected account. Endpoint: GET /v1/boards.
Action
List board usersList the users who have access to a board. Endpoint: GET /v1/boards/{boardID}/users.
Action
List checkboxesList the checklist items on a task. Endpoint: GET /v1/boards/{boardID}/tasks/{taskID}/checkboxes.
Action
List columnsList the columns on a board. Endpoint: GET /v1/boards/{boardID}/columns.
Action
List commentsList the comments on a task. Endpoint: GET /v1/boards/{boardID}/tasks/{taskID}/comments.
Action
List tagsList the tags defined on a board. Endpoint: GET /v1/boards/{boardID}/tags.
Action
List tasksList the tasks on a board. Endpoint: GET /v1/boards/{boardID}/tasks.
Action
Move taskMove a task to a different column or assign it to a user. Endpoint: PATCH /v1/boards/{boardID}/tasks/{taskID}.
Action
Update boardEdit a board's name or settings. Endpoint: PUT /v1/boards/{boardID}.
Action
Update columnRename a board column. Endpoint: PATCH /v1/boards/{boardID}/columns/{columnID}.
Action
Update taskEdit a task's fields. Endpoint: PUT /v1/boards/{boardID}/tasks/{taskID}.
Action
Find funders by querySearch the Crossref Funder Registry for funding organizations matching a free-text query. GET /funders
Action
Find works by querySearch Crossref's bibliographic metadata for works (articles, books, conference papers, etc.) matching a free-text query, with optional filters and sorting. GET /works
Action
Get funderRetrieve metadata for a funding organization and its suborganizations by funder ID. GET /funders/{funder_id}
Action
Get journalRetrieve information about a journal by its ISSN. GET /journals/{issn}
Action
Get memberRetrieve metadata for a Crossref member (publisher) by member ID. GET /members/{member_id}
Action
Get work by DOIRetrieve 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.