Automated MCA Data Entry From Broker Emails
When a broker submission email arrives in your designated Gmail inbox, WebRun reads the merchant name, requested amount, industry, monthly revenue, and broker details, creates a new application record in Centrex with those details pre-filled, and posts a confirmation to Slack so your origination team can see the new file immediately without manual data entry.
How do I automatically create MCA application records from broker submission emails?
When a broker sends a merchant submission to your designated Gmail inbox, WebRun reads the key deal details, checks for duplicates, creates a pre-filled application record in Centrex, and posts a new-file notification to Slack with a direct link. Incomplete emails are flagged rather than partially entered.
- Broker submissions become Centrex records within minutes of the email arriving
- Manual data entry from broker emails is eliminated entirely
- Incomplete submissions are flagged before a partial record is ever created
Built for MCA origination teams · MCA processors · advance underwriters · ISO broker managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
mail.google.comin a real browser with your saved login - no setup, no API keys. -
1
Gmail - read inbound broker submission email
gmail.com
WebRun opens Gmail to read inbound broker submission email. - Monitor the designated broker submission Gmail inbox or label for new emails
- Extract merchant name, requested advance amount, monthly revenue, industry, time in business, and broker name and email
- Flag any email missing key fields for manual review rather than auto-creating a partial record
Done when All key submission details are extracted from the email and validated before Centrex entry.
-
2
Centrex - create application record from email details
centrexsoftware.com
WebRun opens Centrex to create application record from email details. - Check whether an application for this merchant from this broker already exists in Centrex to avoid duplicates
- Create a new application record pre-filled with the extracted details and assign it to the correct origination queue
- Log the source email thread ID on the record for traceability
Done when A new application record exists in Centrex with all available fields populated from the email.
-
3
Slack - post new-file confirmation to origination team
slack.com
WebRun opens Slack to post new-file confirmation to origination team. - Post a new-file notification to the origination Slack channel with merchant name, requested amount, and broker name
- Include a direct link to the new Centrex application record
- Flag any submission email with missing fields so someone can complete the record manually
Done when Your origination team has a Slack notification for every new inbound submission with a link to the Centrex record.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
What if the email is missing key details like the monthly revenue?
WebRun flags incomplete emails in Slack rather than creating a partial Centrex record. Your team can then request the missing information from the broker before the record is created.
Will it create duplicate records if the same broker sends the same merchant twice?
It checks for an existing application with the same merchant name and broker in Centrex before creating a new record. Potential duplicates are flagged in Slack for your team to review.
Which email inbox or label does it monitor?
You specify the Gmail inbox label or address to watch when setting up the workflow. Only emails in that label are processed, so your main inbox is unaffected.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.