Skip to main content

How to automate actions with webhooks

V
Written by Victor Fteha
Updated this week

MCA Pilot can automatically send deal data to external tools whenever specific events occur—like when an offer is created, a deal status changes, or a submission happens. This lets you trigger automations in Zapier, Make, n8n, Go High Level, or any platform that accepts webhooks.

Before you begin: You'll need a webhook URL from your automation platform (Zapier, Make, n8n, etc.). Most platforms provide this when you create a new webhook trigger.

Setting up a webhook workflow

Navigate to SettingsWorkflows in MCA Pilot.

Workflows tab showing list of configured workflows

Configure your workflow:

  1. Webhook URL — Paste the webhook URL from your automation platform

  2. Event — Select which event triggers the webhook (see available events below)

  3. Notification options (optional) — Choose whether to notify originators, closers, or both when this event fires

Click Save. MCA Pilot will now POST deal data to your webhook URL whenever the selected event occurs.

Available events

Common events include:

  • Offer Created — Fires when a new offer is added to a deal

  • Deal Status Updated — Fires when a deal moves to a new status

  • Deal Originators Updated / Deal Closers Updated — Fires when team assignments change

Each webhook payload includes the full deal data (UUID, created date, funder info if available, and event-specific fields). Use this data in your automation platform to update CRMs, send notifications, or trigger follow-up workflows.

Example use cases

  • Auto-tag in Go High Level — When an offer is created, send deal data to GHL and apply an "Offer Received" tag

  • Slack notifications — Post to a Slack channel whenever a deal reaches "First Approval" status

  • CRM sync — Update deal stages in your external CRM whenever MCA Pilot deal status changes

  • Email campaigns — Trigger a Mailchimp or ActiveCampaign sequence when a funding application starts

Webhook URLs must be publicly accessible. If using Zapier/Make/n8n, copy the webhook URL from your trigger step before configuring the workflow in MCA Pilot.

Testing your webhook

After saving, trigger the event manually (e.g., create a test offer) and check your automation platform's webhook logs to confirm the data arrives. Most platforms show recent webhook deliveries and payloads for debugging.

Did this answer your question?