The Workflow Library

Library / Sales ops / sales-ops-013

Create a "log next step" task automatically after a call is logged with no follow-up set

Sales opsContactSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A rep who logs a call without also creating a follow-up task gets a nudge task automatically, closing the gap where a call gets logged and then nothing happens next.

Workflow map Enrollment, branches and actions at a glance sales-ops-013
flowchart TD
    A[Call logged for contact] --> B[Delay 1 hour]
    B --> C{Next activity date still unknown?}
    C -->|Yes| D[Create log-next-step task for contact owner]
    D --> E[Set Missing follow-up nudge date]
    C -->|No| F[End, follow-up already exists]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when calls regularly get logged with no next step, and deals stall not because the rep did not call, but because nobody scheduled what happens after the call.
  • UseUse it as a hygiene layer, not a replacement for coaching reps on setting next steps as part of their own call-wrap habit.
  • SkipDo not use it for high call-volume teams doing rapid dial sessions where a short "no answer" call is logged every few minutes; scope the trigger to connected or meaningful calls only, see Variants.
  • SkipDo not set the buffer delay too short; a rep who steps away to grab coffee before logging the next-step task will get a nudge for work they were already about to do.
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.3 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.4 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.PDF, Markdown, JSON
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

or the sales ops pack, 39 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.