Outcome. The moment a rep logs a note mentioning a known competitor, they get a task with a direct link to that competitor's battlecard, instead of digging through a shared drive mid-deal.
Workflow map
Enrollment, branches and actions at a glance
sales-ops-033
flowchart TD
A[Note logged on deal] --> B[Custom code: scan note text against Competitors list]
B --> C{Competitor match found?}
C -->|Yes| D[Set Competitor mentioned]
D --> E[Create battlecard review task for deal owner]
C -->|No| F[End, no action]
When to use it, when not to
- UseUse it when your team maintains a maintained list of competitors with a battlecard link for each, and reps log discovery and call notes on the deal record.
- UseUse it when the current process is "ask in Slack if anyone has faced this competitor," which is slow and inconsistent.
- SkipDo not use it if competitor mentions mostly happen in call transcripts or emails rather than typed notes; this fiche only scans note text, not other engagement types (see Variants).
- SkipDo not use it without an Enterprise-tier subscription; this fiche depends on a custom object to hold the competitor list and battlecard links, and custom objects require Sales Hub, Service Hub, or Data Hub Enterprise (https://knowledge.hubspot.com/object-settings/create-custom-objects).
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.5 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
