Integration
Connect Conversion Tools to Basin
When something happens in Conversion Tools, your agent does the next thing in Basin. 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 Basin 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 Basin
Triggers and actions 5 triggers ยท 13 actions
Trigger
Conversion FailedTriggered when a file conversion fails, giving the reason it failed.
Trigger
Conversion Result AvailableTriggered when a finished conversion has its result file ready to download.
Trigger
Conversion StartedTriggered when a new file conversion is submitted, while it is still queued or running.
Trigger
Conversion Successfully FinishedTriggered when a file conversion finishes successfully.
Action
Convert FileUploads 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.
Action
Convert File and Get the ResultUploads a file to Conversion Tools, converts it, waits for the conversion to finish and returns a link to download the result.
Trigger
New SubmissionTriggers when your form receives a submission.
Action
Add formCreate a new form under a project. POST /api/v1/forms.
Action
Add projectCreate a new project (form-organizing container). POST /api/v1/projects.
Action
Delete formDestroy a form. DELETE /api/v1/forms/:id.
Action
Delete submissionDestroy a submission. DELETE /api/v1/submissions/:id.
Action
Get formRetrieve a single form by id. GET /api/v1/forms/:id.
Action
Get submissionRetrieve a single submission by id. GET /api/v1/submissions/:id.
Action
List formsList all forms accessible to the account. GET /api/v1/forms.
Action
List projectsList all projects accessible to the account. GET /api/v1/projects.
Action
List submissionsList submissions for a form. GET /api/v1/submissions.
Action
Update formUpdate a form's configuration (notifications, spam protection, branding, etc). PATCH/PUT /api/v1/forms/:id.
Action
Update submissionUpdate a submission's state fields (spam, read, trash). PATCH/PUT /api/v1/submissions/:id.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.