Connect form submissions to external tools
Configure integrations as actions on a form. Each action has its own destination settings, field mappings, enabled status, and delivery history.
Choose a destination
Wirechunk supports email notifications, webhooks, AgencyZoom, Agency MVP, HighLevel, and Ricochet360. Open Forms, choose the form, and add the action for the destination you use.
| Destination | Configuration |
|---|---|
| Recipient email, optional recipient name and subject | |
| Webhook | The receiving HTTP endpoint |
| AgencyZoom | The destination webhook URL and supported field mappings |
| Agency MVP | Organization ID and supported field mappings; delivery also requires Wirechunk’s configured provider connection |
| HighLevel | Token, location ID, and supported field mappings |
| Ricochet360 | The destination webhook URL and supported field mappings |
Use credentials and destination values supplied for the account that should receive the inquiry. If your organization uses several locations or pipelines, confirm which one the connection addresses.
Map the fields
For named providers, connect your form’s stable field identifiers to the destination’s supported fields. Map either a full name or the required first-name and last-name fields. HighLevel and Ricochet360 also require a phone mapping.
The supported fields vary by provider. Use the choices shown in the form editor rather than assuming every CRM field can receive a value. Webhooks send all submitted fields and do not use per-field mappings.
Save, publish, and verify
Save the action and publish the site. Submit a clearly labeled test inquiry from the live form, then inspect both Form entries and the destination tool. Check names, contact information, and any service details you mapped.
Form actions are part of the published configuration. Saving a new token or mapping in the draft does not change the current live form until publication.
Handle a delivery failure
Inspect the entry’s delivery status. Confirm credentials, destination URLs, required mappings, and whether the external service is available. A retry uses the destination configuration saved with that inquiry. Publishing a changed action affects future submissions; it does not rewrite an old delivery. Restore a temporarily unavailable destination before retrying. If an old entry has an unusable destination or credential, use its saved details for manual follow-up or contact Wirechunk for help.
Spam entries may have delivery suppressed. Review the spam classification before attempting to resolve what looks like a missing delivery. A successful form submission and a successful external delivery are separate results.