Integration
Connect TestLocally to MagicSlides
When something happens in TestLocally, your agent does the next thing in MagicSlides. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want TestLocally and MagicSlides 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 TestLocally and MagicSlides
Triggers and actions 1 trigger ยท 6 actions
Trigger
New TestTriggers when a new test has been requested.
- Find Tests
Finds recent Test Results
- Get Random Locations
Returns a set of 1-9 random Location names
- Get Test Results
Gets the Test Result details
- Request New Test
Request a new screenshot from a set of locations
Action
Generate presentation from templateGenerates a presentation using a specific named template and returns per-slide HTML plus PPTX/PDF download links. POST https://www.magicslides.app/api/cli/generate-html-template. Header auth x-api-key. Body: topic (required), templateKey (required, from List presentation templates), slides (3-20, default 7), language (default "en"), presentationType, presentationTone, presentationFor. Returns {success, mode, templateKey, slideCount, presentUrl, pptxUrl, pdfUrl, slides:[{index,html}]}.
- List presentation templates
Lists the 30+ available HTML/PPTX presentation templates and their keys. GET https://www.magicslides.app/api/cli/templates (optional query param mode=proslides to filter to HTML-output templates only). Header auth x-api-key. Returns template keys used as templateKey in Generate Presentation From Template. Response is a JSON array/list of {key, name, ...} objects.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.