Integration
Connect CRUSH to Chinese Text Project
When something happens in CRUSH, your agent does the next thing in Chinese Text Project. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CRUSH and Chinese Text Project 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 CRUSH and Chinese Text Project
Triggers and actions 1 trigger ยท 7 actions
Trigger
Receive NoteTriggers when a new note is captured in CRUSH. Returns the note's transcript and the date it was created.
- Create Note
Creates a new note in CRUSH from the transcript text you provide. Returns the id of the note that was created.
Action
Find texts by titleSearches the textual database and wiki for items matching part or all of a given title. GET https://api.ctext.org/searchtexts?title=...
- Get character
Returns basic data about a single Chinese character. GET https://api.ctext.org/getcharacter?char=...
- Get text info
Returns metadata (title, author, dynasty, etc.) about a textual object identified by its CTP URN. GET https://api.ctext.org/gettextinfo?urn=...
- List dictionary headwords
Returns the complete list of headwords for distinct word senses, names, and places in the CTP dictionary. GET https://api.ctext.org/getdictionaryheadwords
- List dynasties
Returns a list of identifiers, labels, and dates for Chinese dynasties used in the Chinese Text Project. GET https://api.ctext.org/getdynasties
- List texts
Returns the complete list of top-level textual items (books) in the textual database and wiki. GET https://api.ctext.org/gettexttitles
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.