agentOS Native CRM Connector — Deep Dive
agentOS Native CRM Connector
Available from: v1.0.48
NurtureHub's agentOS connector is a purpose-built integration that replaces manual data entry and generic middleware with a direct, real-time bidirectional link between NurtureHub and agentOS. Contacts, activity events, and nurture outcomes flow automatically between both systems so your CRM and your nurture platform always agree.
Overview
| Capability | Direction | Details |
|---|---|---|
| Contact sync | agentOS → NurtureHub | New and updated contacts pushed via webhook |
| Field mapping | Both | agentOS fields mapped to canonical NurtureHub contact model |
| Activity events | agentOS → NurtureHub | Viewings, valuations, offers become engagement signals |
| Nurture outcomes | NurtureHub → agentOS | Emails sent, engagement scores, hot lead status written back |
Authentication
The connector handles the full agentOS authentication lifecycle on your behalf. During setup, you authorise NurtureHub once via Settings → Integrations → agentOS. Credential exchange, token refresh, and re-authentication on expiry are managed automatically — no manual API key management is required after the initial connection.
Contact Synchronisation
Incoming: agentOS → NurtureHub
Contacts flow from agentOS into NurtureHub through two complementary mechanisms:
- Webhook push — agentOS sends a real-time notification to NurtureHub's webhook receiver the moment a contact is created or updated. NurtureHub processes the payload and upserts the contact record within seconds.
- Field mapping — Every agentOS contact field is mapped to the canonical NurtureHub contact model. Standard fields (name, email, phone, address) are mapped directly. Property-specific fields such as applicant type, tenancy status, and property interest are preserved and used to auto-suggest the most appropriate nurture category (e.g. Seller, Landlord, Active Tenant).
Outgoing: NurtureHub → agentOS
NurtureHub writes the following nurture outcomes back to the corresponding agentOS contact record:
- Emails sent — a log entry is created for each email delivered as part of a nurture sequence.
- Engagement score — the current NurtureHub intent score is written to the contact record and updated as it changes.
- Hot lead status — when a contact crosses the hot lead threshold, a flag and timestamp are written back to agentOS, ensuring agents working inside their CRM are immediately aware.
Activity Event Ingestion
AgentOS activity events are consumed as first-class engagement signals in NurtureHub's real-time intent scoring engine:
| agentOS Event | NurtureHub Signal | Scoring Impact |
|---|---|---|
| Viewing booked | Property interest confirmed | Moderate positive |
| Viewing completed | Active buyer/tenant engagement | Strong positive |
| Valuation booked | Seller/landlord intent signal | Strong positive |
| Offer submitted or progressed | High-intent transaction signal | Triggers hot lead review |
Activity events are processed as they arrive via the agentOS API and are reflected in intent scores and hot lead alerts in near real-time.
Webhook Receiver
NurtureHub exposes a dedicated webhook endpoint for agentOS push notifications. Webhook registration is performed automatically during the connection setup flow — no manual URL configuration is required in agentOS.
Supported webhook events:
contact.createdcontact.updated
All webhook payloads are verified using the agentOS signing mechanism before processing.
Setup
- Navigate to Settings → Integrations → agentOS in your NurtureHub dashboard.
- Click Connect agentOS and complete the authorisation flow.
- NurtureHub will register the webhook endpoint with agentOS automatically.
- A full contact import runs on first connection. Subsequent updates arrive in real time.
- Review the field mapping summary and confirm the default nurture category assignments before going live.
Prerequisites:
- An active agentOS account with API access enabled.
- A NurtureHub account on any paid plan.
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Contacts not appearing in NurtureHub | Webhook not registered | Disconnect and reconnect the integration to re-register |
| Scores not writing back to agentOS | API token expired | NurtureHub will re-authenticate automatically; check the connection status indicator |
| Activity events not affecting scores | agentOS activity sync disabled | Confirm API access includes activity log permissions in your agentOS account settings |