kvCORE

kvCORE

· #148 most-used

The CRM that runs every deal, from first click to closed key

CRMSalesMarketingEmailAutomation

kvCORE is the all-in-one real-estate platform that brokerages and their agents use to capture leads, nurture contacts, run drip campaigns, and manage the full transaction pipeline in one place. Connect it to Actionist and your agent can create contacts the moment a lead arrives, advance pipeline stages after every showing, fire campaign enrolments on behavioural signals, and keep every record current — all without a rep touching the keyboard. The result: faster speed-to-lead, a database that reflects reality, and agents spending time on relationships rather than data entry.

Average time saved
10 hours
per person · per month
1 workdays back

Eliminates manual work. Agents manually copying lead data between portals, updating pipeline stages after every showing, and logging call notes into the CRM typically burn 2–3 hours per day — kvCORE automation eliminates all three.

Schedule

What your kvCORE agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
TueThu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

kvCORE × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~46 hrsSaved / week
6Personas served
For customer success
Featured4 apps

New lead to first touch in 90 seconds

The moment a new buyer lead lands in kvCORE from any portal, your agent reads the full record, checks the lead's property preferences, updates their stage to 'Engaged', and fires a personalised introductory email — all before a human has opened their laptop. The rep's Slack channel gets a summary card with the lead's source, preferred zip codes, and budget range, and a follow-up appointment slot is dropped on their Google Calendar for the next morning. No lead leaves the first hour uncontacted.

~13 hrs / week

Time saved for your team — every week, on autopilot

The flow
Trigger·When a new lead is created in kvCORE via the New Lead webhook
Result
Update lead stage to Engaged and add notePost lead summary card to assigned rep's channelCreate follow-up appointment for rep
The win
Saved per run
25 min
Runs / week
~30×
Sub-2-minute speed to lead, every time
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    18 min / week
    Manual lead logging

    Reps type contact details from portal emails into kvCORE by hand, one lead at a time, during prime selling hours.

    Sales Agent
    0 min
    Agent creates contacts on arrival

    Every inbound lead is captured, tagged by source, and enrolled in the right nurture sequence the moment the webhook fires — before the rep's phone has buzzed.

  • Marketing
    13 min / week
    Campaign enrolment batches

    Marketing manually exports a filtered contact list, imports it into the campaign tool, and enrols contacts — a weekly batch job taking the whole morning.

    Marketing Agent
    0 min
    Behavioural trigger enrolment

    The agent watches campaign action events in kvCORE and enrols or advances contacts the instant they click, view, or submit — no batch window, no export.

  • Customer Support
    18 min / week
    Post-call note entry

    After every client call the support agent opens kvCORE, finds the contact, and types up the outcome, objections, and next step — eating 5 minutes per call.

    Customer Support Agent
    0 min
    Agent logs call notes instantly

    The agent listens for the call-completed signal and adds a structured note to the kvCORE contact record within seconds, so the rep can move straight to the next call.

  • Human Resources
    7 min / week
    New-agent CRM setup

    When a new agent joins, HR or ops manually creates their CRM profile, assigns territory tags, and configures pipeline stages — 30–45 minutes per onboard.

    Human Resources Agent
    0 min
    Agent provisions CRM profile

    On a new hire trigger, the agent creates the kvCORE contact record, assigns tags matching the territory map, and creates an onboarding task for the broker — done in under a minute.

  • Finance
    13 min / week
    Commission-close data entry

    After each closing, the finance team cross-references kvCORE, a spreadsheet, and the transaction management tool to pull the commission split data for invoicing.

    Finance Agent
    0 min
    Agent extracts and routes close data

    The agent reads the kvCORE lead record at close, updates the stage to Past Client, and pushes the deal data directly to the finance tracker and HubSpot — one source, zero copy-paste.

  • Operations
    25 min / week
    Prospect-import QA

    Operations manually checks each row of a new contact import against kvCORE to catch duplicates before uploading, a process that grinds to a halt on lists over 100 rows.

    Operations Agent
    0 min
    Agent deduplicates on import

    For every incoming prospect row, the agent searches kvCORE by email first; duplicates get a tag update and note, new records get created and enrolled — clean database on every import.

  • Legal
    6 min / week
    GDPR erasure logging

    Legal receives an erasure request, manually finds the contact in kvCORE, deletes the record, and then documents the action in a compliance spreadsheet — per-request overhead adds up.

    Legal Agent
    0 min
    Agent executes erasure and logs it

    The agent receives the erasure request, deletes the kvCORE contact, and appends a timestamped compliance record to the Google Sheet — the audit trail is complete before Legal has closed the email.

+ 100s of other kvCORE automations
Average monthly
10 hrs / person / month
Average monthly
10 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 people
Hourly rate
$20 / hr
Hours saved / week
25
Hours saved / year
1,250
Annual ROI
$25,000

Based on kvCORE's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug kvCORE into Actionist

Pick the connection method that suits your environment.

The fastest path to a live kvCORE connection. Install the kvCORE MCP server in one click and the agent reaches your leads, contacts, and campaigns through a permissioned session — no API tokens to rotate, no webhook endpoints to maintain.

1
Open the Apps tab

Find kvCORE in the Apps library and click Connect. MCP is selected by default.

2
Authorise in kvCORE

You'll be redirected to insiderealestate.com to grant Actionist read/write access to your kvCORE account. Choose the brokerage workspace you want the agent to operate in and confirm.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

6 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with kvCORE

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.
MCP servers

MCP servers that work with kvCORE

Connect Actionist to MCP servers built for or around this app.

No MCP servers indexed for this app yet.
FAQs

Questions about kvCORE + Actionist

How does Actionist connect to kvCORE?
The recommended path is MCP — open the Apps tab, click Connect on kvCORE, and authorise through your Inside Real Estate account. Actionist provisions a permissioned session scoped to the workspace you choose. No API tokens to manage. If you prefer direct API access, switch to the API Token method in the connection settings and paste the token from kvCORE's Settings → Integrations → API Access page.
Which kvCORE permissions does the agent need?
For the full action set — creating and updating contacts, managing tags, enroling in campaigns, creating tasks, and reading pipeline stages — the agent needs Contacts read/write, Leads read/write, Campaigns write, and Tasks write scopes. If you're only using read actions for reporting, you can restrict to read-only scopes. MCP handles scope selection during the authorisation flow; API Token users configure scopes when generating the token in kvCORE.
Can the agent fire both triggers — New Lead and Campaign Action — at the same time?
Yes. Each trigger is an independent webhook subscription in kvCORE. You can have an agent watching New Lead for instant contact creation and a second agent watching Campaign Action for behavioural enrolment in parallel — they don't interfere. If both fire on the same contact (a new lead who immediately clicks a campaign link), both agents act independently; the second agent's Get Contact step will see the record the first agent just created.
How do I avoid creating duplicate contacts when leads come from multiple sources?
Build a Search Contacts step as the first action before any Create Contact call. The agent queries kvCORE by the lead's email address; if a record comes back, it runs Update Contact instead of Create Contact. This deduplication pattern catches portal leads, manual entries, and import rows arriving in parallel. The Search Contacts action returns the existing record's ID, which you chain into the update call.
What happens if I disconnect kvCORE while a campaign-action trigger workflow is running?
In-flight workflow runs that have already started will complete their current step, then fail on the next kvCORE action with an authentication error. Actionist logs the failure with the contact ID and payload so you can re-trigger manually after reconnecting. Trigger subscriptions pause immediately on disconnect — no phantom webhook deliveries. Reconnect in the Apps tab and your trigger workflows resume listening from that moment; they don't replay missed events.
Can the agent update a lead stage and then enrol the contact in a campaign in the same run?
Yes — chain Update Lead Stage and Add Contact to Campaign as sequential steps in a single workflow. kvCORE processes them as separate API calls; the stage update fires first, then the campaign enrolment. The typical pattern is: trigger fires → Get Lead (read current stage) → Update Lead Stage (advance) → Add Contact to Campaign (enrol in next sequence). Each step's output is available to the next, so the campaign ID can be derived from the stage you just set.
Does the New Lead trigger fire for leads I create manually inside kvCORE?
Yes — kvCORE's webhook fires on any new lead record creation regardless of origin: IDX portal, Zillow sync, manual entry, API creation, or import. If you want the agent to skip leads it created itself (to avoid a loop), add a step that checks the lead source tag or a custom field you stamp on agent-created records, and exit the workflow early if that marker is present.
How many kvCORE API calls does a typical workflow consume, and are there rate limits?
A five-step workflow with one read and one write against the kvCORE API makes two API calls per run. kvCORE enforces rate limits at the account level (typically 60–120 requests per minute depending on your plan tier). For high-volume brokerage operations running 50+ concurrent workflows, stagger trigger schedules or add a brief delay step between calls. If you hit a rate limit, Actionist retries with exponential back-off up to three times before logging the failure.