Custom integrations

Everre can pull records from a system of yours on its own — a listing platform, a county portal, a vendor's API — every morning, into your properties, people or companies. You do not write the mapping. You tell the assistant what the system is, add the key where it asks you to, and check what it proposes.

There are two things involved, and it helps to know the names.

A connection is the system: one address, and the key that lets Everre in. It lives in Settings → Integrations.
A feed is what runs on its own against that connection: which records to ask for, what each becomes, and when. Feeds show in Settings → Integrations and, like everything that runs on its own, in Home → Automations.

Public records

Some feeds are already written. Under Settings → Integrations → Public records are county and city datasets, mapped and checked against the source, free to pull:

Building permits — Cook County and — City of Chicago: work, amount and status, on the properties you hold.
Building violations — City of Chicago: opened and closed as inspectors record them.
Building code scofflaw list — City of Chicago: buildings whose owners the city has taken to court, with the owner named and the case number.
Commercial valuations — Cook County: the assessor's income valuation of every commercial parcel in a township — units, size, market value, and the EGI, NOI and cap rate behind it. This one creates properties.

Choose Set up, narrow it to the part of the region you work — a township, a minimum permit cost — and it becomes a feed like any other: preview it, turn it on. Or ask the assistant: "Add Chicago building violations for the properties we hold."

Permits, violations and court listings appear on each property under Public Records, newest first. They attach only to properties you already have; a permit for a building you don't hold is passed over, and the preview says how many.

The City of Chicago asks that anything built on its data carry its disclaimer, which is on the dataset in settings.

Setting one up with the assistant

Say what you want, in your own words:

Connect our listings from Acme. Their API is at api.acme.com and they gave me a key.

The assistant creates the connection and hands you a link to add the key. Paste the key there, never into the chat. It is stored encrypted, it is never shown again, and the assistant never sees it — that is the point of the link.

With the key in place, the assistant looks at what the system answers with — the shape of it, not the whole thing — and proposes a feed: which records, and which of their fields become which of yours. Then it previews the feed and shows you what a run would do: how many records would be created, how many you already have that would be updated, and a sample of five. If that looks right, say so and the assistant turns the feed on. The first pull happens within the minute; after that it runs daily at the hour on the feed.

Everything the assistant can do here, you can also do from the settings screen — and from Claude, if you have connected it.

What a run does

A run asks the system for its records — only the ones changed since the last run, where the system supports that — and turns each into a record of yours.

Nothing duplicates. Each record is matched on the system's own id, so a run over the same records again updates them rather than creating them twice. A record you already had from elsewhere is matched the way an import matches — on parcel number, address, name or email.

The source's values stay current, and yours stand. A value the feed wrote moves when the system's value changes — a new assessed value, a corrected unit count. A value you set is never overwritten: if you typed 24 units and the system says 26, your number stands, and the run lists it under Kept so you can see the disagreement. Blank fields are filled.

Nothing is deleted. A record that disappears from the system stays with you.

The limits, and why

A feed that reaches a system you do not control needs a few guardrails, and they are worth knowing so they do not surprise you.

A new or changed feed will not run until it has been previewed. The preview is the check that the mapping is right; a feed that could run blind after an edit is a feed that writes the wrong thing at 6am.
A run that would create more than the feed's limit stops and asks. The default is 500 new records. A vendor that returns everything instead of what changed would otherwise turn into thousands of properties overnight. You will get a notification; open the feed and choose Go ahead anyway, or raise the limit on the feed. Permit and violation feeds create no records, so the limit does not apply to them.
Three failed mornings in a row pause the feed and tell whoever set it up. The run history on the feed says what happened each time.
A run can be undone. Open the feed, find the run under Recent runs and choose Undo. Everything that run created — records, permits, violations — is deleted; anything it only filled in is kept, because you had it first.

Where the key can and cannot go

The connection's address is fixed by whoever set it up, and every request a feed makes stays under it — a feed cannot be pointed somewhere else. The key is sent only to that address. If a mapping ever contains something that looks like a key, Everre refuses to save it and says where the key belongs.

When it looks quiet

A morning with nothing new and a run that failed look the same from the property table. Home → Automations shows every feed with its last run; opening one shows the recent runs, what each found, and the error if there was one. A run that suddenly finds nothing where the last one found records is flagged — usually the system changed the shape of its response, and the assistant can look again and adjust the mapping.