Connect a developer-built application form to MCA Pilot with a webhook so every merchant submission creates a deal, and assign those deals to the right rep. This guide covers getting your webhook URL, the fields MCA Pilot maps, form-to-rep assignment, and verifying your first test submission.
Before you start
You need a form or application that can send submissions to an HTTP callback or webhook URL, and access to that form's webhook settings. First-time setup requires MCA Pilot support to generate your webhook URL and map your form fields to deal fields.
If your form runs on Jotform or DocuSeal, use the platform-specific setup instead — see How to integrate your application form with MCA Pilot.
Get your webhook URL
MCA Pilot generates a unique webhook URL for each application form integration. Request yours via the blue chat icon in MCA Pilot, email [email protected], WhatsApp wa.me/15559026222, SMS +1 833-610-4177, or invite [email protected] to your company Slack channel.
Your URL follows this format: https://webhook.mcapilot.com/nln4oez113cp7t/{GUID} — the GUID is unique to your integration.
If your integration uses the old https://n8n.mcapilot.com/webhook/ format, it no longer works. Update to the current Hookdeck base URL — see How to update your webhook URL to the new Hookdeck format.
Add the webhook to your form
Paste your webhook URL into the form's webhook or HTTP callback settings, wherever your platform exposes them. Save the settings and confirm the URL is present before you test.
Fields MCA Pilot maps
MCA Pilot maps your form's fields to deal fields, and the mapping is created with support. The mapped fields cover the business name, monthly revenue, and the merchant's contact and ownership details.
Share your form's current field names or builder access so the mapping matches what your form actually sends. If you rename a field or add a question later, send the updated field names to support — a renamed field can silently stop populating the deal.
No fields are required for the webhook to create a deal — a submission creates a deal even without a company name. Include a company name anyway so you can identify the deal in MCA Pilot, and pass as much merchant information as your form collects. Many of our 20 API funder integrations require certain fields, so a fuller submission gives them the best chance of going through.
If a deal is created with empty fields, see Edit deal fields after an application form generates a deal to fix the deal and request a mapping update for future submissions.
Assign the form to a rep
Deals auto-assign to the rep whose form ID is on their profile, so each rep needs their own form. Set up the assignment in MCA Pilot:
Copy the form ID for the rep's specific form from your form platform.
In MCA Pilot, open Settings → Workspace, click the rep, then click Edit in the top right.
Paste the form ID into the Unique App ID field and click Done.
When a merchant submits that rep's form, the deal is created and assigned to the rep automatically. Deals are only auto-assigned when the form ID is linked to a rep profile.
For new reps, clone the existing form in your platform, copy the same webhook URL into the clone, and add the clone's form ID to the new rep's profile. You do not need a new webhook URL unless you build a completely new integration. If the rep has no account yet, add them first — see How to Add a New Rep into MCA Pilot.
Test the integration
Submit a test application from the rep's actual form, then confirm the deal in MCA Pilot before going live.
Submit a test application with realistic merchant data.
Open MCA Pilot and locate the new deal.
Confirm the deal is assigned to the expected rep.
Confirm the business name, owner details, and monthly revenue match the submitted values.
If the form includes file uploads, confirm the files appear on the deal.
No fields are required for the webhook to create a deal, but include the company name and merchant details in the test submission so you can find and verify the deal in MCA Pilot.
Submit one test application and check the result before submitting again; replaying a form submission can create duplicate deals instead of updating the existing one.
If bank statements or other files come from a separate form, that form must post to the same webhook URL and pass the business name from the main form into a hidden field via a URL parameter, so MCA Pilot can match the files to the correct deal. See Receive application files through a webhook and verify deal attachments for the full attachment workflow.
What to check when a submission does not create a deal
Work through these checks in order when a submission produces no deal in MCA Pilot.
Confirm the webhook URL. The URL in the form's webhook or HTTP callback settings must be exactly the URL support provided and start with
https://webhook.mcapilot.com/nln4oez113cp7t/. Oldhttps://n8n.mcapilot.com/webhook/andhttps://n8n.fundmore.io/webhook/URLs no longer work — replace the base URL and keep the GUID. See How to update your webhook URL to the new Hookdeck format.Confirm the form is live. The form must be published and the webhook or HTTP callback must be saved and active in the form platform.
Check the rep mapping. The rep's profile must have the form ID in the Unique App ID field; deals are only auto-assigned when the form ID is linked to a rep profile.
When the deal appears with empty fields, the submission's mapped field names likely changed — send the current field names to support to remap.
When the deal appears but files are missing, see Receive application files through a webhook and verify deal attachments.
Need more help?
Reach us through the blue chat icon in MCA Pilot, email [email protected], WhatsApp wa.me/15559026222, SMS +1 833-610-4177, or invite [email protected] to your company Slack channel.