Integration
Connect Formstack Documents to Clay
When something happens in Formstack Documents, your agent does the next thing in Clay. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Formstack Documents and Clay 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 Formstack Documents and Clay
Triggers and actions 1 trigger · 19 actions
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.
Action
Create Record in TableAdds a record (row) to a Clay table by posting it to that table's webhook URL. Each key in the record becomes a column in the table.
Action
Get my userReturns the Clay user the connection authenticates as. Takes no search criterion.
Action
Get Search Results PageReturns the next page of people or company records for a Clay search you already created. Call it repeatedly while it reports that more results are available.
Action
Search People or CompaniesStarts a search of Clay's people or company database using structured filters, and returns a search ID. Use Get Search Results Page to read the matching records.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.