Keep visitor records in step with onboarding changes
Make an approved onboarding correction travel to the right visitor record, so you do not have to remember a second update later.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Visitor
Tool to update an existing visitor for a given form. Use when you have the formId and visitorId and need to modify visitor details. Only include fields you want to change.
Why this helps
Correcting a document but forgetting the related visitor record creates repeat work and uncertainty in the next interaction.
- Carry approved corrections through to the associated visitor record.
- Reduce duplicate updates after onboarding changes.
- Use the visitor ID to keep the task focused on the intended record.
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 apply approved onboarding corrections.
- 3Write one plain-language instruction asking Notis to update only the specified visitor with approved details supplied in the PDF revision request.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with a controlled correction and inspect the resulting visitor record.
Questions about this workflow
Can it overwrite every visitor detail?
Your instruction should name only the approved details to change. The action supports updating selected visitor information.
What identifiers should I provide?
Include the Formdesk form ID and visitor ID so Notis can target the correct record.
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.