Automated Data Entry from Processor Emails to IRIS CRM
When a processor email arrives in Gmail matching your defined rules (approval confirmations, chargeback notices, or monthly reports), WebRun reads the key fields, finds or creates the matching merchant record in IRIS CRM, updates the relevant data fields, and posts a summary to Slack so your team knows what was updated.
How do I automatically enter processor email data into IRIS CRM?
WebRun monitors Gmail for incoming processor emails matching your rules, extracts the key fields, and updates the matching merchant records in IRIS CRM automatically. Unmatched emails are flagged for manual review. Your team gets a Slack summary of every change so nothing is updated without visibility.
- Processor emails update IRIS CRM records within minutes of arrival, not hours
- Manual copy-paste data entry is eliminated for known merchant records
- Unmatched emails are flagged in Slack so nothing slips through unreviewed
Built for payment ISOs · ISO operations teams · merchant services back-office · boarding administrators
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 - detect and read incoming processor email
gmail.com
WebRun opens Gmail to detect and read incoming processor email. - Monitor Gmail for incoming emails from processor domains or matching your subject-line rules
- When a match arrives, read the email body and extract key fields: merchant name, MID, transaction amounts, chargeback details, or approval status
- Categorize the email type (approval, chargeback, report, or other) to determine which IRIS CRM fields to update
Done when The inbound email is read and its data is extracted and categorized.
-
2
IRIS CRM - update or create matching merchant record
iriscrm.com
WebRun opens IRIS CRM to update or create matching merchant record. - Search IRIS CRM for the merchant record matching the MID or merchant name from the email
- Update the relevant fields: approval status, chargeback count, processing volume, or notes depending on the email type
- If no matching record exists, create a new lead record and flag it for your team to review
Done when The IRIS CRM record is updated (or a new one is flagged for review).
-
3
Slack - post summary of what was updated
slack.com
WebRun opens Slack to post summary of what was updated. - Post a summary to the operations Slack channel listing what was updated: merchant name, field changed, old value, and new value
- Flag any email where no matching IRIS CRM record was found so the team can review it manually
- Include a direct link to the updated IRIS CRM record for quick access
Done when The team has a summary of all IRIS CRM updates and any unmatched emails in Slack.
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
Will it create or overwrite IRIS CRM records without my review?
It updates existing records automatically for known MIDs, but any email with no matching record creates a flagged draft entry in IRIS CRM for your team to review before it is saved.
How does it know which emails to process?
You define the processor email addresses and subject-line patterns during setup. Only emails matching those rules trigger a data entry run.
What if the email data is in an attachment rather than the body?
WebRun can read structured attachments such as CSV or PDF statements if you configure that during setup. Plain-text and HTML email bodies are handled automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.