Integration
Connect WebAsk to Vector Express v2.0
When something happens in WebAsk, your agent does the next thing in Vector Express v2.0. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want WebAsk and Vector Express v2.0 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 WebAsk and Vector Express v2.0
Triggers and actions 1 trigger · 9 actions
Trigger
Send ResponsesTriggers when send survey responses anywhere.
Action
Create surveyCreate a new survey in a WebAsk folder.
Action
Delete surveyDelete a survey/quiz by id. DELETE /quiz/{id}.
Action
Get surveyGet a single survey/quiz by id, including its questions/widgets. GET /quiz/{id}.
Action
Get survey summaryGet aggregated summary/analytics for a survey's responses. GET /quiz/{id}/summary.
Action
List responsesList answers/responses submitted to a survey. GET /quiz/{id}/answers.
Action
List surveysList all surveys/quizzes in the workspace. GET /quiz (supports pagination/filtering per WebAsk API v3 docs).
Action
List workspacesList the account's workspaces (used to select where surveys/folders live). GET /service/workspaces.
Action
Get conversion pathFind the sequence of converters needed to go from one vector format to another. GET /api/v2/public/convert/{from}/auto/{to}/ — returns the chain of converter endpoints to POST the file through in order.
Action
Optimize SVGRun the svgo optimizer on an SVG file to reduce file size. POST the file body to /api/v2/public/convert/svg/svgo/svg/.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.