Integration
Connect EasyCSV to Fillout Forms
When something happens in EasyCSV, your agent does the next thing in Fillout Forms. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want EasyCSV and Fillout Forms 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 EasyCSV and Fillout Forms
Triggers and actions 2 triggers ยท 7 actions
Trigger
New Spreadsheet Row ImportFires instantly for each row/record as EasyCSV imports a spreadsheet. In EasyCSV, open your import's Sheet Details, check "Post imports to Webhook", and paste this trigger's minted URL. EasyCSV sends one POST per row; the payload binds as {{ trigger.body.* }} (record_data holds the row's column values, plus import_id/import_name/sheet_name/importer_email metadata).
- Create CSV File
Creates a CSV File that can be used in your Zap, automatically emailed as an attachment, or uploaded to a specific place via SFTP.
- Parse CSV File
Parse a CSV file and return a JSON array of rows
Trigger
New SubmissionTriggers when a form receives a new submission.
- Add Submission
Create a new submission on a form programmatically. POST /forms/{formId}/submissions.
- Delete Submission
Delete a submission from a form by ID. DELETE /forms/{formId}/submissions/{submissionId}.
- Get Submission
Retrieve a single submission by ID for a given form. GET /forms/{formId}/submissions/{submissionId}.
- List Forms
Retrieve all forms in the account. GET /forms.
- List Submissions
Retrieve all submissions for a given form, with filtering/pagination. GET /forms/{formId}/submissions.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.