Zapier & Webhooks: Custom SmartForm Automations

Use Native Connections First

For GoHighLevel, HubSpot, Pipedrive, and ClickFunnels, use the native connection flow first:

How to Connect Your CRM to SmartForm

Native connections handle authentication and provider-specific field behavior without a separate Zap.

Use Zapier or a custom webhook when:

• Your destination is not available in Connections
• You need an additional custom workflow
• You need to fan out SmartForm data to another application

Avoid accidental duplicates: if a CRM is connected natively and your Zap also creates a contact in that CRM, one submission may create/update the contact twice.

Create a SmartForm Webhook

Quick path: Widgets → select widget → Webhooks → add webhook

1. Open the widget's Webhooks tab.
2. Add a webhook and give it a clear name.
3. Choose the event:
4. • Lead Created
   • Booking Created
4. Paste the receiving endpoint URL.
5. Add/use the webhook secret if your receiver supports verification.
6. Click Test Webhook and confirm a successful HTTP response.

Send the Webhook to Zapier

1. In Zapier, create a Zap with Webhooks by Zapier.
2. Choose Catch Hook.
3. Copy the URL generated by Zapier.
4. Paste it into the SmartForm webhook.
5. Save and click Test Webhook.
6. Submit one real test lead through the widget if Zapier needs a full sample payload.
7. Return to Zapier and select the newest sample.

Alternative: Use the SimpleCheck Zapier App

Accounts with Developer API access can use the SimpleCheck Zapier app's polling trigger instead of Catch Hook:

1. Open Developer API in the portal.
2. Enable/reveal the API token.
3. In Zapier, open the SimpleCheck app and authenticate with API Key.
4. Use the New Lead trigger for lead-only or booking-lead submissions.
5. Use the submission id as the deduplication key.

This path reads saved submissions from the Developer API. The Catch Hook path above is the simpler real-time option when Developer API access is not enabled.

Map the Destination Action

Add the destination app/action in Zapier, then map only fields returned by your sample. Common fields include:

• First name / last name
• Email / phone
• Widget/client ID
• Credit score
• Available/spendable credit
• DTI
• Income
• IP address
• Assigned person and booking time (for bookings)

If the destination needs custom fields, create those fields first, then refresh the Zapier field list.

Field availability varies. Failed or unmatched X-Ray checks will not contain the same credit values as a successful report.

Test Before Turning the Zap On

1. Use contact details you control.
2. Submit the live widget.
3. Confirm SmartForm saved the lead.
4. Confirm Zapier received the event.
5. Confirm the destination created/updated the expected record.
6. Turn the Zap on only after the mapping is correct.

Troubleshooting

Zapier cannot find a sample

Click Test Webhook, then submit a fresh live lead. Make sure the webhook is enabled and uses the correct event.

The webhook test fails

Confirm the URL is HTTPS, has no spaces, and is still active. Review the HTTP status returned by Test Webhook.

Credit fields are empty

Use a sample from a successful X-Ray pull. Do not invent defaults for missing financial data.

The CRM receives duplicates

Check whether the same CRM is connected natively. Disable either the duplicate Zap action or the native destination, depending on your intended flow.

For help, contact support through the portal or email support@simplecheck.ai with the widget name, event type, destination host, and test time.

Updated on: 23/07/2026