Actions5
- Form Actions
- Submission Actions
Overview
This node interacts with the Fillout API to manage form submissions. Specifically, the Delete Submission operation allows users to delete a particular submission from a specified form. This is useful in scenarios where you need to programmatically remove outdated, incorrect, or unwanted submission data from your Fillout forms.
Practical examples include:
- Automatically deleting test submissions after QA.
- Removing submissions that do not meet certain criteria.
- Cleaning up submissions based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| Form | The form from which the submission will be deleted. Options are dynamically loaded forms. |
| Submission ID | The unique identifier of the submission to delete. |
Output
The output JSON contains a confirmation of the deletion operation:
{
"success": true,
"message": "Submission <submissionId> deleted successfully"
}
Where <submissionId> is the ID of the deleted submission.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Fillout API.
- The node makes HTTP DELETE requests to the Fillout API endpoint for submissions.
- Proper configuration of the API URL and authentication token is necessary.
Troubleshooting
- Error deleting submission: This can occur if the submission ID or form ID is invalid, or if the API key lacks permissions. Verify that the form and submission IDs exist and that the API key is valid.
- Network or authorization errors: Ensure the API key credential is correctly set up and has access rights.
- Submission not found: If the submission ID does not exist under the specified form, the API will return an error. Double-check the submission ID.
- API rate limits: Excessive deletion requests may trigger rate limiting; consider adding delays or retries.
Links and References
- Fillout API Documentation (for detailed API endpoints and authentication)
- n8n documentation on creating custom nodes