Integration
Connect Conversion Tools to Easybill
When something happens in Conversion Tools, your agent does the next thing in Easybill. 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 Easybill 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 Easybill
Triggers and actions 4 triggers ยท 16 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 customerCreate a new customer. POST /customers
- Add document
Create a new document (invoice, quote, etc). POST /documents
- Add project
Create a new project. POST /projects
- Add task
Create a new task. POST /tasks
- Add time tracking
Create a new time tracking entry. POST /time-trackings
- Delete customer
Delete a customer. DELETE /customers/{id}
- Delete document
Delete a document. DELETE /documents/{id}
- Get customer
Fetch a single customer by id. GET /customers/{id}
- Get document
Fetch a single document by id. GET /documents/{id}
- List documents
Fetch a list of documents. GET /documents
- List projects
Fetch a list of projects. GET /projects
- List tasks
Fetch a list of tasks. GET /tasks
- Update customer
Update an existing customer. PUT /customers/{id}
- Update document
Update an existing document. PUT /documents/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.