Integration
Connect Conversion Tools to Emailr
When something happens in Conversion Tools, your agent does the next thing in Emailr. 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 Emailr 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 Emailr
Triggers and actions 4 triggers ยท 14 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.
Action
Add contactCreate a contact. POST /v1/contacts
Action
Add segmentCreate a contact segment. POST /v1/segments
Action
Add templateCreate an email template. POST /v1/templates
Action
Delete contactDelete a contact by ID. DELETE /v1/contacts/{id}
Action
Delete segmentDelete a segment by ID. DELETE /v1/segments/{id}
Action
Delete templateDelete a template by ID. DELETE /v1/templates/{id}
Action
Get contactFetch a contact by ID. GET /v1/contacts/{id}
Action
Get templateFetch a template by ID. GET /v1/templates/{id}
Action
List segmentsList contact segments. GET /v1/segments
Action
Update contactUpdate a contact by ID. PUT /v1/contacts/{id}
Action
Update segmentUpdate a segment by ID. PUT /v1/segments/{id}
Action
Update templateUpdate a template by ID. PUT /v1/templates/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.