Finish approved field cleanup after a process change
Close the loop on a process revision by removing a field that has been explicitly retired from the related intake workflow.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Delete Field in Formdesk
Tool to delete a specific field in a Formdesk form. Use after confirming formId and fieldId.
Why this helps
Old fields can linger after a document process changes, leaving people unsure which questions still matter.
- Finish a confirmed cleanup action in the same process-change handoff.
- Reduce clutter from fields no longer used by the workflow.
- Keep field removal tied to an explicit approval and identifier.
Setup
Build it in a few focused steps.
- 1Connect FileToPDF.dev and Formdesk to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to remove fields confirmed as retired.
- 3Use one plain-language instruction asking Notis to delete only the specified Formdesk field after an approved process change, with its form ID and field ID.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test on a safe form and verify the intended field is removed.
Questions about this workflow
Should this remove fields automatically whenever a PDF changes?
No. Use it only when the process change explicitly approves retirement of a specific field.
What references are needed?
Provide the Formdesk form ID and exact field ID for the approved removal.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link FileToPDF.dev to Formdesk. A trigger fires from one place; an action lands in another.
FileToPDF.dev triggers
Formdesk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Automatic Login
Tool to perform automatic login to Formdesk and retrieve an access token. Use when you need to authenticate with username and password.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Formdesk Entry
Tool to submit a new entry to a Formdesk form. Use after collecting all form field values to send a new entry for a specific formId. Example: "Submit entry to form 12345 with first_name='Bob', email='bob@example.com'."
Create Field
Tool to create a new field in a specific Formdesk form. Use after you have the formId and need to extend the form schema with an additional input.
Create Visitor
Tool to add a new visitor to a specific Formdesk form. Use when you need to register a visitor's metadata (e.g., name, email) before submitting entries.
Delete Formdesk Entry
Tool to delete a specific entry from a Formdesk form. Use after confirming the target entry exists.
Delete Field in Formdesk
Tool to delete a specific field in a Formdesk form. Use after confirming formId and fieldId.
Delete Form in Formdesk
Tool to delete a specific form. Use when you need to permanently remove a form after confirming it's no longer needed.
Delete Visitor in Formdesk
Tool to delete a specific visitor in a Formdesk form. Use after confirming formId and visitorId.
Connect any two apps with Notis in the middle.
FileToPDF.dev and Formdesk, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Formdesk.