Integration
Connect Conversion Tools to NEXT
When something happens in Conversion Tools, your agent does the next thing in NEXT. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Conversion Tools 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 Conversion Tools and NEXT
Triggers and actions 4 triggers ยท 17 actions
Trigger
Conversion FailedTriggered when a file conversion fails, giving the reason it failed.
- Conversion Result Available
Triggered when a finished conversion has its result file ready to download.
- Conversion Started
Triggered when a new file conversion is submitted, while it is still queued or running.
- Conversion Successfully Finished
Triggered when a file conversion finishes successfully.
- Convert File
Uploads a file to Conversion Tools and starts converting it, returning the conversion ID. Use one of the result triggers or Convert File and Get the Result to pick up the converted file.
- Convert File and Get the Result
Uploads a file to Conversion Tools, converts it, waits for the conversion to finish and returns a link to download the result.
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.