Integration
Connect Openlayer to Formstack Documents
When something happens in Openlayer, your agent does the next thing in Formstack Documents. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Openlayer and Formstack Documents 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 Openlayer and Formstack Documents
Triggers and actions 3 triggers · 37 actions
Trigger
New ProjectTriggers when a new project is created in your Openlayer workspace.
Trigger
New Test ResultTriggers when a new test result is available for a data source. Useful for alerting on passing or failing model tests.
Action
Create Data SourceCreates a new data source in a project for streaming production data to Openlayer.
Action
Create ProjectCreates a new AI or ML project in your Openlayer workspace.
Action
Create TestCreates a data quality test in a project. Checks for duplicate rows, null values, or row counts.
Action
Delete Inference PipelineDelete an inference pipeline by its ID. DELETE /inference-pipelines/{id}
Action
Delete ProjectDelete a project by its ID. DELETE /projects/{id}
Action
Delete TestDelete a test by its ID. DELETE /tests/{testId}
Action
Evaluate TestEvaluates a test for a specific time range. Use after publishing records to get immediate results.
Action
Find Data SourceFinds a data source (inference pipeline) by name in a project.
Action
Find ProjectFinds a project by name in your Openlayer workspace.
Action
Find Test ResultFinds test results for a data source, including whether each test passed or failed. Filter by outcome or test type to branch an automation on the result.
Action
Get Inference PipelineRetrieve the details around a specific inference pipeline. GET /inference-pipelines/{id}
Action
Get ProjectRetrieves one project by its id. Openlayer has no single-project endpoint, so this reads the workspace's first 100 projects and returns the one matching the id.
Action
Get TestRetrieve a test by ID. GET /tests/{testId}
Action
Get Test ResultRetrieves one test result by its id. Openlayer has no single-result endpoint, so this reads the data source's 100 most recent results and returns the matching one.
Action
List Inference PipelinesList the authenticated user's inference pipelines under a project. GET /projects/{id}/inference-pipelines
Action
List ProjectsLists the projects in your Openlayer workspace, optionally narrowed to one kind of project. Returns up to 100 projects.
Action
List Test ResultsList all results for a test/goal under an inference pipeline. GET /inference-pipelines/{id}/results or GET /tests/{id}/results
Action
List TestsLists the tests in a project, optionally narrowed by kind, archived state or monitoring mode. Returns up to 100 tests.
Action
Publish RecordPublishes an LLM inference record to a data source for monitoring. Streams the model input, output, and metadata to Openlayer.
Action
Update Inference PipelineUpdate an inference pipeline. PUT /inference-pipelines/{id}
Action
Update ProjectUpdate a project. PUT /projects/{id}
Action
Update TestUpdate a test (partial updates allowed). PUT /tests/{testId}
Trigger
New Merged DocumentTriggers when a merged/populated document is created.
Action
Combine FilesJoins several files into one PDF or Word document. Give it the files in the order you want them, either as links or as base64 content, and it returns the combined file.
Action
Convert File to PDFTurns a Word, Excel, PowerPoint, image or HTML file into a PDF. Point it at the file with a link or supply the file content, and it returns the PDF.
Action
Copy DocumentMakes a copy of one of your Formstack Documents templates under a new name, and returns the new document with its merge key, merge URL and available merge fields.
Action
Create Data RouteCreates a data route in Formstack Documents — a single endpoint that sends one set of data to several documents at once, following the rules you give it. Returns the new route with the URL to post data to.
Action
Create Data Route MergeSends one set of data into a Formstack Documents data route, which merges it into every document the route's rules select. Optionally returns the finished documents in the response.
Action
Create DocumentCreates a new document template in Formstack Documents from HTML or from an uploaded PDF, Word, Excel or PowerPoint file, and returns its merge URL and the merge fields found in it.
Action
Delete Data RouteDeletes a data route from Formstack Documents. The documents the route pointed at are not deleted.
Action
Delete DocumentDeletes a document template from Formstack Documents.
Action
Get Data RouteReturns one Formstack Documents data route, with its name, its merge URL and the rules that decide which documents the data goes to.
Action
Get DocumentReturns one document template from Formstack Documents, with its name, type, output format, merge URL and — for HTML templates — the template's HTML.
Action
Get Document FieldsReturns the merge fields found in a Formstack Documents template, so you know which names to send when merging data into it.
Action
List Data RoutesReturns your Formstack Documents data routes, each with its name, key and the URL to send data to.
Action
List DocumentsReturns your Formstack Documents templates, each with its name, type, output format and merge URL.
Action
Update Data RouteUpdates a Formstack Documents data route — its name, folder, or the rules that decide which documents receive the data. Anything you leave blank stays as it is.
Action
Update DocumentUpdates a Formstack Documents template — its name, folder, output format, filename or the template content itself. Anything you leave blank stays as it is; the template type cannot be changed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.