Email Parser CINC Integration: Parse Real Estate Lead Emails into CINC
CINC imports leads. MailParse turns the lead email into the fields CINC imports.
Every portal, landing page, and referral partner sends leads as email, each in its own layout. CINC will happily take those leads once they are structured, through the CSV import tool, the public API, or a Zapier action. What no CINC setting does is read the body of a message from a source CINC has no native integration with and turn it into a first name, last name, email, cell phone, property address, and price. MailParse parses those values out of the body and out of HTML tables, and hands you clean CSV and JSON.
Last updated August 2026
Connect a mailbox to pull .eml/.msg in bulk, or paste a raw email to test the converter now.
Create a free account to download. No credit card required.
CINC creates leads from its own lead generation sources and from a CSV upload, but it has no way to read an arbitrary lead notification email and pull the name, phone, property address, and price out of the body into lead fields. MailParse does that half. Name the fields you want, and it returns clean CSV for the CINC import tool or JSON you post through the CINC public API, Zapier, or Make.
- Named fields
- Name, phone, address and price from the body
- HTML alerts
- Parses the table layout portals send
- CSV / JSON
- Bulk import or API into CINC
- No code
- Name fields, skip the custom build
CINC, short for Commissions Inc, is built for high producing real estate teams, and it is good at the part of lead handling that follows capture: routing to an agent, pipeline stages, drip campaigns, and reporting on who actually worked the lead. It also has honest ways in. The import tool takes a CSV, where first name, last name, email, and cell phone are the fields that make a lead usable, with source, lead type, assigned agent, and pipeline status as the ones worth adding. There is a public API for two way partner integrations, which CINC opens up by request through [email protected]. Zapier is available on the Ramp, Pro, and Select plans, and the CINC app there has a create lead action. CINC also ships prebuilt connections to sources like Zillow, DotLoop, and Mojo Dialer.
The gap sits one step earlier. Leads do not arrive as CSV rows. They arrive as email: a portal alert, a form notification from a team website, a referral from a relocation partner, an open house sign in summary, a builder or iBuyer notice. Each sender formats the message differently, and the values a team needs are prose inside the body. Nothing native to CINC reads that body and decides that the digits after "Phone:" are the cell phone and that the line under the photo is the property address. If CINC has a prebuilt integration with the source, use it and skip this page entirely. If it does not, the usual outcome is an assistant retyping leads into CINC, which is slow enough that speed to lead suffers, and error prone enough that the phone number is wrong on the lead you most wanted to call.
MailParse is the parser that closes that gap. Connect the Gmail, Outlook, Microsoft 365, or IMAP mailbox your lead alerts land in, or forward one sample message to a parsing address, then name the fields you want: first_name, last_name, email, cell_phone, property_address, list_price, lead_type, source. MailParse reads them out of the full body and out of HTML lead alerts with real tables, which most portals send and which a plain text view flattens into a wall of characters. You get a clean CSV, an Excel workbook, or JSON. From there the data reaches CINC the way that suits your team: upload the CSV through the import tool, post the JSON through the CINC public API, or hand the fields to Zapier or Make and let the create lead action build the record. MailParse records the filename of any attachment for reference, but it does not read the data locked inside a PDF or spreadsheet file, so when a referral packet carries the details as an attachment, extract that file with a document tool first. This page is an honest look at where CINC native handling is enough and where a parser does the work it cannot.
What the converter does
Everything you need to turn a pile of email files into a spreadsheet your team can actually use.
Lead fields pulled out of the body
A forwarded portal alert is one long message to CINC. MailParse reads the buyer name, cell phone, property address, list price, and the question they asked, and returns each as its own column, so the CSV you upload maps straight onto CINC lead fields instead of needing an assistant to retype it.
Parses HTML lead alerts and tables
Portals and team sites send lead notifications as HTML with tables and images, not plain text. MailParse parses those table rows, so a digest listing several inquiries comes through as clean columns, one row per lead, ready for a bulk import.
One setup covers many senders
Zillow, your IDX site, a relocation partner, and an open house app all describe the same lead differently. Name the fields once and MailParse finds them across layouts, so you are not maintaining a separate rule set for every source CINC has no connector for.
CSV for the import tool, JSON for the API
Download a CSV shaped for the CINC import tool with first name, last name, email, and cell phone in place, or take JSON and post it through the CINC public API or a Zapier create lead action. The same parse feeds whichever route your plan supports.
Backlogs, not just new mail
Point MailParse at a whole label or folder of old lead alerts and get one combined spreadsheet. Teams switching CRMs or cleaning up a shared inbox use this to recover months of leads that never made it into CINC at all.
Accurate and private
Phone formats, unicode names, and accented street names come through intact, no field is silently dropped, and your email is never used to train AI. Files are deleted after processing.
How to parse a lead email into CINC
Four steps from a portal alert sitting in an inbox to a lead record in CINC.
Connect or forward
Connect the Gmail, Outlook, Microsoft 365, or IMAP mailbox your lead alerts arrive in, or forward one sample message to a parsing address to test the layout first.
Name your lead fields
Pick the values you want as columns: first_name, last_name, email, cell_phone, property_address, list_price, lead_type, and source. Those first four are what CINC needs to make the lead usable.
Pick CSV or JSON
Take a CSV shaped for the CINC import tool, or JSON if you would rather post through the public API or a Zapier create lead action.
Load into CINC
Upload the CSV in the import tool, or let the API or Zapier build the lead per email. Save the setup and every future alert from that sender parses the same way.
Who needs a parser in front of CINC
Real estate teams whose leads arrive from sources CINC has no prebuilt connector for.
Team leads and ISAs
Inside sales agents lose the first call when a lead sits in an inbox waiting to be typed in. Parsing the alert into a CINC ready row cuts the delay between the email arriving and the agent seeing a lead worth calling.
Referral and relocation networks
Relocation companies and referral partners email leads in their own formats and are rarely in any CRM marketplace. One parsing setup per partner turns those messages into clean rows without a custom build.
IDX and custom team websites
A home grown IDX or a WordPress form emails the inquiry rather than pushing to CINC. Parse the notification and the lead lands in CINC with the property address and price attached, not just a name.
Brokerages consolidating CRMs
Moving agents onto CINC from Realvolve, Follow Up Boss, or a shared inbox means recovering leads that only ever existed as email. Bulk parse the archive into one spreadsheet, then import it in a single pass.
MailParse vs native CINC lead capture
Reads the message body
CINC ingests leads that are already structured. MailParse is what turns an unstructured lead alert into those fields in the first place.
No connector required
Prebuilt CINC integrations cover the big portals. A parser covers everyone else, including the referral partner who will never build one.
HTML tables, not flattened text
Lead digests that list several inquiries in a table come back as one row per lead instead of a paragraph an assistant has to read.
Works before the API decision
The CINC public API is available by request to partners. Parsing to CSV needs no API access at all, so a team can start today.
Ways to get lead emails into CINC, compared
A CINC team has a few honest routes from a lead email to a lead record, and the right one depends on whether the source has a connector and how much you want to build. Here is the side by side, with credit to each native path where it wins. For the wider CRM picture see the email to CRM guide, and to push fields as JSON, the email parser API.
| What matters | MailParse | Native CINC integration | Manual entry or CSV by hand | Custom build on the CINC API |
|---|---|---|---|---|
| What it does | Parses the lead email into named fields, then exports CSV or JSON for CINC | Pushes leads from a supported source such as Zillow straight into CINC | A person reads the email and types the lead into CINC or into a sheet | A developer writes against the CINC public API to create leads |
| Sources it covers | Any sender that emails you, including partners with no connector | Only the sources CINC has built a connection for | Anything, at the cost of a person per lead | Anything, once you have built the parsing yourself too |
| Where CINC wins | Does not route, drip, or report; it stops at clean data | Best route by far when it exists: no parsing step, nothing to maintain | No cost and no setup for a handful of leads a month | Two way sync and record updates a parser does not attempt |
| HTML tables and digests | Table rows become one row per lead | Not applicable, the source sends structured data already | Read and retyped by hand | Possible, but you write and maintain the parsing logic |
| Setup and upkeep | Name the fields once, no code, adjust when a sender changes layout | Turn it on in CINC, nothing to maintain | None, but the work repeats on every single lead | API access by request, plus developer time to build and keep working |
| Speed to lead | Runs as mail arrives, so the lead is ready in seconds | Effectively instant | As fast as somebody is watching the inbox | Instant once built |
CINC capabilities described here reflect published CINC documentation as of August 2026, including the CSV import tool, the public API offered to partners through [email protected], and Zapier availability on the Ramp, Pro, and Select plans. Platforms change, so verify against your own account before you build. CINC and Commissions Inc are trademarks of their owner and Realvolve is a trademark of its owner. MailParse is not affiliated with either. No pricing is implied here.
Frequently asked questions
Does CINC have an email parser?
No. CINC brings leads in through its prebuilt lead source integrations, a CSV upload in the import tool, its public API, and Zapier. None of those reads an arbitrary email body and decides which words are the name, the cell phone, and the property address. That extraction step happens outside CINC, either by a person retyping the lead or by a parser such as MailParse.
How do I import leads into CINC?
Use the CINC import tool with a CSV file. First name, last name, email, and cell phone are the fields that make a lead usable, and source, lead type such as buyer or seller, the assigned agent, and pipeline status are worth including too. If your leads are sitting in email rather than in a spreadsheet, parse them into that CSV shape first, then upload once.
Does CINC have an API?
Yes. CINC describes a public API that lets a third party build a deep two way integration with the CRM, and it invites partners to request access by emailing [email protected]. That is the route for creating and updating leads programmatically. It does not replace parsing, because the API expects fields you have already extracted from wherever the lead came from.
How do I get Zillow leads into CINC?
Use the native connection. CINC lists prebuilt integrations with sources including Zillow, DotLoop, and Mojo Dialer, and when a connector exists it is always the better route: nothing to parse and nothing to maintain. A parser is for the sources with no connector, such as a relocation partner, your own IDX site form, or an open house app that only emails you.
Can I connect CINC to Zapier?
Yes, on the Ramp, Pro, and Select plans, which opens up thousands of Zapier apps and a create lead action for CINC. Pair that with a parser and the flow is simple: the lead email arrives, MailParse returns clean JSON fields, and the Zapier action creates the CINC lead with the phone and address already in the right places.
How do I parse a real estate lead email into a CRM?
Forward one sample of each alert type to a parser and name the values you want as fields, typically first name, last name, email, cell phone, property address, and price. The parser learns where those sit in that sender layout, then handles every future message the same way and outputs CSV for an import or JSON for an API or Zapier action.
Does this work with Realvolve and other real estate CRMs?
Yes, because the parsing step is CRM agnostic. MailParse turns the lead email into named fields and gives you CSV or JSON; what changes per CRM is only how you load it. Realvolve, Follow Up Boss, kvCORE, and CINC all accept an import file or take records through Zapier, so the same parse feeds any of them.
Can MailParse read data inside email attachments?
No. MailParse parses the email body and HTML tables, and it records the filename of any attachment for reference, but it does not read the data locked inside a PDF, Word, or spreadsheet file. When a referral packet carries the lead details as an attachment, extract that file with a document tool first, then feed the result into your CINC import.
Turn the lead email into a row CINC can import
Forward one lead alert and watch the name, cell phone, property address, and price come back as clean columns, ready for the CINC import tool, the API, or a Zapier create lead action.