Integration
Connect Fillout Forms to Rendi
When something happens in Fillout Forms, your agent does the next thing in Rendi. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Fillout Forms and Rendi 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 Fillout Forms and Rendi
Triggers and actions 1 trigger · 10 actions
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.
Action
Delete FileDeletes one stored file in Rendi by file_id. DELETE /v1/files/{file_id}.
- Get File
Returns the details of one stored file — its status, download link, size, format and media properties.
- List Commands
Lists FFmpeg commands previously sent to Rendi. GET /v1/commands.
- Poll FFmpeg Command
Get the status of a previously submitted FFmpeg command
- Run FFmpeg Command
Submit an FFmpeg command for processing with input and output file specifications
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.