ceven

Fillout Forms

Streams every form submission into your operational workflows, updates respondent records across your stack, and manages form availability based on real time triggers.

Try Fillout Forms in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Fillout Forms integration

    • Describe the outcome and Ceven picks the right Fillout Forms calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Fillout Forms data, across all 22 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Fillout Forms access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Fillout Forms, when, and on whose behalf.
    • The agent pauses and asks when Fillout Forms is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Fillout Forms.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Fillout Forms action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Fillout Forms, and when to use it.

Get forms
Pull a list of all forms in the account to identify the correct form ID for a workflow.
Get form
Retrieve the full configuration and settings for a specific form by its ID.
List submissions
Pull all responses for a specific form, filtered by date or respondent criteria.
Get submission
Pull the detailed response data for a single submission ID to extract specific answers.
Update submission
Modify the data within an existing submission, useful for adding internal notes or status flags.
Delete submission
Remove a specific submission from the Fillout record for data privacy or cleanup.
Create form
Programmatically generate a new form based on a template for a new client or project.
Update form
Change form settings or labels dynamically based on external business logic.
Delete form
Remove an outdated form from the account to keep the workspace clean.
Search submissions
Query submissions using specific keywords or values to find a particular respondent.
Get account info
Pull current account limits and plan details to ensure API quotas are not exceeded.
Authorize OAuth
Generate the URL to redirect users to the Fillout consent page for account connection.
Invalidate Access Token
Tool to revoke an existing oauth access token. use when the user logs out or you need to programmatically invalidate a token after deauthorization. example: "invalidate token abcdefg123456". this endpoint does not return a json body. succes

13 actions · scroll to see them all

Frequently asked questions

Ceven connects to Fillout via webhooks or polling depending on your plan. When a user hits submit, Fillout sends the payload to Ceven, which then parses the fields and maps them to your chosen destination. You can set up filters so that only submissions containing specific answers trigger a workflow. For example, if a user selects urgent in a priority dropdown, Ceven can immediately ping a Slack channel and create a high priority ticket in Jira. This happens in real time, meaning the gap between submission and action is usually just a few seconds.
Yes. Using the create form action, Ceven can spin up new forms programmatically. This is particularly useful for agencies that onboard new clients every week and need a fresh intake form for each one. You can define the fields and settings in your workflow, and Ceven will push that configuration to Fillout. Once created, the agent can take the resulting form URL and email it to the client or embed it in a portal, ensuring a consistent data collection process without manual setup.
Ceven can process as many submissions as your Fillout API plan allows. It is important to note that Fillout enforces rate limits on their REST API to ensure platform stability. If your workflow triggers a massive burst of API calls, such as updating thousands of submissions at once, you may hit a 429 rate limit error. Ceven handles this by implementing an exponential backoff strategy, meaning it will pause and retry the request automatically until it succeeds, so no data is ever lost during high traffic spikes.
Yes, Ceven can use the update submission action to modify data. This is commonly used for internal enrichment. For instance, if a user submits a form with a company name, Ceven can search a database for that company, find the industry and employee count, and then write those details back into the Fillout submission record. This keeps the Fillout dashboard as a complete source of truth for both user provided data and AI enriched data without needing a separate spreadsheet.
Ceven uses OAuth for secure access. When you connect your account, you are redirected to Fillout to grant specific permissions. Fillout then provides Ceven with an access token and a refresh token. We store these tokens encrypted at rest. We never ask for your password and we do not store your master API key. If you ever want to stop the integration, you can revoke access directly from your Fillout account settings, which immediately kills the token and stops all active workflows.
Ceven provides the tools to maintain compliance by automating data deletion. You can build a workflow that triggers the delete submission action after a set period of time or upon a user request. Because the agent can search for submissions by email, it can find all records associated with a specific person and purge them from Fillout across multiple forms. This ensures you are not storing personally identifiable information longer than necessary and helps you adhere to right to be forgotten requests.
If a form is deleted, any workflow attempting to read from or write to that form ID will receive a 404 not found error from the Fillout API. Ceven catches this error and sends a notification to the workflow owner. You can configure an error handling path that alerts you via email or Slack so you can update the workflow with the new form ID. To prevent this, we recommend using a naming convention for forms and avoiding manual deletions of forms that are actively linked to live agents.
Absolutely. This is one of the most powerful ways to use the integration. You can tell the agent to look at a specific field in the submission payload. If the answer matches a certain value, it follows one path; if it matches another, it follows a different one. For example, if a customer selects billing as their reason for contact, Ceven routes the data to the finance team. If they select technical support, it routes the data to the engineering team, ensuring the request reaches the right person instantly.

Alternatives to Fillout Forms

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Typeform logoTypeformJotform logoJotformGoogle Forms logoGoogle Forms

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Fillout Forms and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free