Webhooks send form data to your other systems the moment a patient submits. No exports, no copy-pasting.
What Webhooks Do
When a patient submits a form, Formisoft sends the data as a JSON payload to a URL you choose: a practice management tool, a Slack channel, a custom API, or anything that accepts an HTTP POST. Add several webhooks to one form to update several systems at once.
Setting Up a Webhook
- Open the form you want to connect.
- Go to the Settings tab.
- Scroll to the Webhooks section.
- Enter the destination URL.
Click See Example to preview the payload and map fields on the receiving end.
HMAC Signature Verification
Every request carries an HMAC signature header. Verify it on your server to confirm the data came from Formisoft and wasn't altered in transit.
When Webhooks Fire
Webhooks fire once the submission is complete: all pages done, conditional logic resolved, payment processed. You never get partial data.
What's in the Payload
The payload includes:
- All field responses from the submission
- Form metadata (form ID, submission timestamp)
- Patient information, if linked to a patient record
- Appointment details, if the form includes scheduling
- Payment data, if collected through Stripe
Testing and Debugging
Submit a test, then click See Last Requests to see the response code, timing, and any error from the receiving server.
Common Use Cases
- Send completed intake data to the system your team already uses
- Create tickets or records in practice management software
- Trigger appointment confirmation emails
- Push submissions to analytics or reporting tools
- Kick off patient onboarding workflows
Need help setting up webhooks? Reach out at support@formisoft.com.
Get every patient ready before they walk in.
- Forms, consents, and signatures before the visit
- Your paper forms converted by AI
- BAA included