Salesforce stores your pipeline. GoWarmCRM executes on it. Nightly diagnostics, playbook triggers on Opportunity stage change, AI-drafted action queues — all tracked in a dedicated GoWarm Action custom object and surfaced on Salesforce Calendar. Your Tasks stay clean.
GoWarmCRM connects via the Salesforce REST API using OAuth 2.0. It reads your existing data without modification, and writes GoWarm Actions to a dedicated custom object — keeping your standard Task and Activity objects entirely untouched.
GoWarmCRM authenticates via OAuth 2.0. A lightweight managed package installs the GoWarm Action custom object and Calendar schema — the safest Salesforce-supported way to deploy custom objects. No changes to Opportunities, Contacts, Tasks, or any standard object. Works with Enterprise and Unlimited editions.
Your existing Salesforce Opportunity stage names are mapped into GoWarmCRM's diagnostic and playbook configuration. No changes to Salesforce stage definitions or pipeline structure — GoWarmCRM reads and adapts to what you already have.
GoWarmCRM reads Salesforce every night, runs diagnostics, and writes resulting actions to the GoWarm Action object. Each action surfaces on Salesforce Calendar. Playbooks also trigger immediately on Opportunity stage change — not just at night.
| Object | What GoWarmCRM reads | What GoWarmCRM writes | Mode |
|---|---|---|---|
| Opportunity | Stage, value, close date, owner, stage history | — | Read |
| Contact | Name, email, linked Opportunities | — | Read |
| Account | Name, industry, linked Opportunities | — | Read |
| GoWarm Action Custom Object | Completion status, rep notes, snooze state | Action title, trigger reason, priority, AI suggestion, linked Opp/Contact, due date, playbook step reference, completion state | Read + Write |
| Salesforce Calendar | Existing meetings and events (for signal context) | GoWarm Actions surfaced as calendar items — visible alongside existing meetings | Read + Write |
| Task / Activity Optional | Existing logged activities (diagnostic context) | Optional: a Salesforce Task is created when a GoWarm Action is marked complete — configurable per org, off by default | Read |
Salesforce Tasks were designed for manually logged activity records — calls, emails, to-dos reps create themselves. Injecting GoWarmCRM's system-generated action queue into the Task object creates immediate problems: rep task lists fill with diagnostic alerts they didn't create; existing Process Builder flows and Apex triggers may fire unexpectedly on bulk inserts; and third-party apps reading the Activity timeline see GoWarmCRM data mixed into their signal.
The GoWarm Action custom object solves all of this. It is a purpose-built schema — with fields for trigger reason, AI suggestion, priority score, linked Opportunity and Contact, playbook step reference, snooze state, and completion tracking. GoWarmCRM owns this object entirely. Your Salesforce Task object stays exactly as it is.
Every GoWarm Action is also written to Salesforce Calendar as a dated item — so reps see their action queue directly in the Salesforce calendar view they already use, alongside existing meetings and events. No new tab required. If your team also wants completed GoWarm Actions to appear in the native Activity timeline, Task write-back is available as a configurable opt-in.
When GoWarmCRM reads completion, it reads two sources: the GoWarm Action object (for explicit rep completion), and directly from email and calendar signals — so if a rep sends an email to a stalled deal without logging anything, the next nightly diagnostic detects the two-way contact and resolves the action accordingly. The system doesn't rely on rep-logged completions to stay accurate.
Salesforce is exceptional at storing pipeline data. What it doesn't do is tell a rep what to do when an Opportunity has been in Proposal for 18 days and there's been no two-way email contact in two weeks. GoWarmCRM provides the diagnostic engine, the action queue, and the calendar surfacing — all writing to a clean, purpose-built schema in Salesforce.
Salesforce handles what happened and stores your pipeline. GoWarmCRM handles what happens next — and surfaces it where reps already work, including the Salesforce calendar.
| Salesforce | GoWarmCRM | |
|---|---|---|
| Primary role | System of record — stores pipeline data and history | System of action — tells every rep what to do next |
| Action tracking | Native Tasks — manually created by reps; automation can cause noise if bulk-written by external tools | GoWarm Action custom object — system-generated, purpose-built schema, no interference with Task automation |
| Calendar visibility | Manual events and tasks the rep creates | GoWarm Actions automatically surface as Salesforce Calendar items — rep sees their queue without leaving Salesforce |
| Stall detection | Reports run by managers; relies on rep updating Opportunity fields | Automatic — email and calendar signals read directly, independent of Salesforce field updates |
| Playbook execution | Flow / Process Builder — internal Salesforce automations, not rep-facing queued actions | Fires on Opportunity stage change → GoWarm Action created → rep queue updated → calendar item added |
| Completion detection | Relies on rep logging a Task or updating the Opportunity | Reads GoWarm Action status and independent email/calendar signals — accurate even when reps don't log |
Salesforce Tasks were designed for manually logged activity records. Writing GoWarmCRM's system-generated action queue into the Task object creates three problems: rep task lists fill with diagnostic alerts they didn't create; existing Process Builder flows, Apex triggers, and automation logic may fire unexpectedly on bulk inserts; and third-party apps reading the Activity timeline get GoWarmCRM data mixed into their signal.
The GoWarm Action custom object has a purpose-built schema — trigger reason, AI suggestion, priority score, linked Opportunity and Contact, playbook step reference, snooze state, and completion tracking. GoWarmCRM owns this object entirely. Your Task object stays exactly as it is. Task write-back is available as a configurable opt-in for teams that need it.
When a GoWarm Action is created — from a diagnostic alert, a playbook trigger, or a renewal window flag — it is simultaneously written to Salesforce Calendar as a dated event linked to the rep. Reps see their GoWarmCRM action queue in the Salesforce calendar view they already use, alongside existing meetings and events, without opening a separate tab. Marking the action complete in either GoWarmCRM or directly from the calendar item updates both the GoWarm Action record and the calendar entry.
No. The GoWarm Action custom object is net-new — it does not modify, extend, or interact with any existing standard Salesforce objects unless you explicitly enable Task write-back. Your Process Builder flows, Apex triggers, Workflow Rules, and any third-party apps operating on Opportunity, Task, Contact, or Account objects are entirely unaffected. GoWarmCRM reads from those objects but writes only to its own.
GoWarmCRM reads completion from two sources. First, the GoWarm Action object — if the rep marks the action done in GoWarmCRM or via the Salesforce calendar item, the record is updated. Second, GoWarmCRM reads underlying signals directly from email and calendar. If a rep sends an email to a stalled deal without logging anything, the next nightly diagnostic detects the two-way email contact and resolves or adjusts the GoWarm Action accordingly. Diagnostic accuracy doesn't depend entirely on rep-logged completions.
Yes — a lightweight managed package installs the GoWarm Action custom object and the Calendar event schema into your Salesforce org. This is the Salesforce-supported mechanism for deploying custom objects, and ensures that schema upgrades can be applied without your admin making manual field changes. The package installs only what GoWarmCRM needs: the GoWarm Action object and Calendar write permissions. It does not modify any standard Salesforce objects. Works with Enterprise and Unlimited editions.
1–2 weeks. Setup involves: installing the GoWarm managed package, OAuth authorisation to your Salesforce org, mapping your Opportunity stage names into GoWarmCRM, configuring diagnostic thresholds (stall durations, deal value brackets), and seeding your playbooks. No rep training required — the action queue is self-explanatory and calendar items appear automatically. The nightly run starts the evening after setup completes, and reps see their first action queue the next morning.
Book a free 20-minute demo. We'll walk through the GoWarm Action object, how it maps to your Opportunities, and what your reps' calendar looks like on day one.