How to Import Leads into CINC from Email: CSV, API & Zapier

The short version: CINC accepts leads three ways, through a CSV upload in the import tool, through its public API, and through a Zapier create lead action. All three expect fields that already exist. None of them opens a lead notification email and works out which words are the buyer's name and which are the property address. That extraction step happens before CINC, either by a person retyping the lead or by an email parser.

This trips up a lot of teams who assume that because CINC has an open API, getting leads in is solved. The API is genuinely open and genuinely useful. It just starts one step after the problem most teams actually have, which is that half their leads arrive as email from sources CINC has never built a connector for.

How do I import leads into CINC?

Use the import tool with a CSV file. Four fields are what make a lead usable once it lands: first name, last name, email, and cell phone. Beyond those, the ones worth including are source, so you can report on which channel produced the lead, lead type (buyer or seller), the agent the lead should be assigned to, and pipeline status. A row missing the cell phone is a row an ISA cannot act on, so it is worth getting that column right before you upload rather than fixing it inside CINC afterwards.

That covers a spreadsheet you already have. It does not cover the far more common situation, which is 200 lead alerts sitting in a shared inbox in 200 slightly different layouts.

Does CINC have an API?

Yes. CINC publishes 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 right route if you are building software that needs to create and update CINC leads programmatically, or if you want records flowing back out of CINC as well as in.

What the API does not do is parse. It expects a payload with the fields already separated. So if your leads live in email, you still need something in front of it that turns the message into those fields. The API decision and the parsing decision are separate, and you can solve the parsing one today without waiting on API access.

Can I connect CINC to Zapier?

Yes, on the Ramp, Pro, and Select plans, which unlocks thousands of Zapier apps plus a create lead action for CINC. For most teams this is the practical middle path: no developer, no API request, and no CSV to upload by hand.

The flow looks like this. A lead alert arrives in your mailbox. A parser reads the fields you named and outputs JSON. Zapier picks that up and fires the CINC create lead action with the phone number and property address already in the right places. Nobody touches it.

The three routes, compared

Why lead emails are the hard part

A lead notification is written for a human. It says something like "Sarah Whitfield is interested in 418 Maple Court" with the phone number on its own line under a photo of the house, the price somewhere in a table, and a note about financing at the bottom. Every sender arranges that differently. Your IDX site emails one shape, a relocation partner emails another, the open house app emails a third, and the builder you get referrals from emails a fourth.

None of those senders will build a CINC connector. There are too few of them, from CINC's point of view, and too many of them from yours. So the lead sits in an inbox until someone opens it, reads it, and retypes six values into CINC. On a good day that takes two minutes. On a busy Saturday it takes four hours, which is four hours the lead spent going cold.

That delay is the real cost, not the typing. Response time is the single most measurable thing in lead conversion, and a lead that reaches an agent in ninety seconds converts on a completely different curve than one that reaches them the next morning. Teams that get this right pair fast capture with fast contact, whether that is an ISA watching a queue or software that places the first qualifying call the moment a record appears. Neither helps if the record does not exist yet.

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: first_name, last_name, email, cell_phone, property_address, list_price, lead_type, and source. The parser learns where those values sit in that particular sender's layout, then handles every future message from that sender the same way, without anyone opening it.

Output is where the routes converge. Take CSV if you are loading a backlog through the import tool. Take JSON if you are posting through the public API or handing fields to a Zapier create lead action. It is the same parse either way, which means you can start with CSV uploads this week and move to Zapier later without redoing the setup.

One practical detail: name your fields to match the CINC columns from the start. Calling it cell_phone rather than phone saves you a mapping step on every single import, and it makes the CSV readable to whoever inherits the process.

What about the lead digests that list several inquiries?

Some sources batch. Instead of one email per lead you get a daily summary with an HTML table, five rows, each row a separate person. Copying that by hand is where columns get shifted and phone numbers end up attached to the wrong name.

A parser that understands HTML tables returns one record per row, so a five lead digest becomes five clean rows in the CSV rather than one row with everything crushed together. The mechanics are the same as any table in any email, covered in extracting a table from an email without breaking the columns.

What about lead details inside an attachment?

Worth being direct about this. An email parser reads the message body and its HTML tables, and it records each attachment by filename, but it does not open a PDF and read what is printed inside. Relocation packets and some referral networks send the details exactly that way.

When that happens you are looking at a document extraction job rather than an email parsing one. Run the file through a tool built to read documents, then merge that output with the fields the parser pulled from the body. Two steps, but each one uses the right tool rather than the wrong one badly.

When you do not need any of this

If every lead you get comes through a source CINC already connects to, stop here. The native integration is faster, free of maintenance, and there is nothing a parser adds. The same applies at low volume. Six leads a week by email is a job for a person, not a workflow, and building automation around it is a way to spend an afternoon saving four minutes.

The threshold worth watching is not lead count on its own. It is lead count multiplied by how often the person who types them in is unavailable. A single ISA covering weekdays is fine at moderate volume and falls apart the first weekend they take off, and that is usually the moment a team decides the inbox needs to feed the CRM directly.

Where to go next

If your leads arrive from sources CINC has no connector for, the email parser CINC integration page walks through the full setup, from connecting the mailbox to naming fields to choosing between the import tool and the API. For the JSON payload shape you would post through the public API or hand to Zapier, see the email parser API. Running the same problem in a different CRM is close to identical: email to CRM covers the general pattern, and there are dedicated walkthroughs for GoHighLevel and LeadConnector, Pipedrive, and HubSpot. Still deciding on a tool at all? The best email parser guide compares what is on the market and concedes where each one wins.