Args

%{
  "account_id" => "34567",
  "data" => %{
    "account_insight_agent_id" => "da0f9b3e-2ed3-4a0b-a1bf-63344873f9f0",
    "insights" => [
      %{
        "action_plan" => "Start by simplifying the path between initial setup and the first meaningful product signal. If the biggest drop is happening right after the first task, the next step may be asking for too much effort or too much technical confidence all at once. Review the wording, effort required, and perceived value of the second step, and make sure it clearly communicates *why* completing it matters. In many adoption journeys, users stay engaged when they can quickly connect setup work to a visible outcome.\n\nNext, consider restructuring the checklist so that the second and third tasks create a faster sense of progress. You may want to move a lighter-weight task earlier, break one complex step into two smaller milestones, or add supporting guidance that reassures users they are still on the right path. If the current sequence jumps too quickly from \"basic setup\" to \"full implementation,\" users can stall before reaching the point of activation. A shorter and more confidence-building middle section often improves follow-through.\n\nFinally, evaluate the checklist experience as part of the broader onboarding flow rather than as a standalone asset. Look at whether users who abandon the checklist are receiving any follow-up nudges, contextual help, or reinforcement elsewhere in the product. If not, add supporting moments that bring users back to the next task with clearer context. The goal is not only to raise checklist completion, but to help more users cross the threshold from setup into meaningful product usage.",
        "actions" => [],
        "cta_text" => "Review checklist journey",
        "entity_id" => nil,
        "entity_type" => "checklist",
        "expected_impact" => "Reducing this early drop-off could improve activation by helping more new users reach their first successful in-product milestone.",
        "finding" => "Your **Getting Started** checklist appears to create momentum at the top, but that momentum fades quickly after the first completed task.\n\n- **Step 1 completion:** **78%**\n- **Step 2 completion:** **46%**\n- **Full checklist completion:** **29%**\n- Largest drop appears between **\"Install the SDK\"** and **\"Track your first event\"**\n\nThis suggests users may be reaching the setup phase successfully, but not getting to the moment where Appcues begins to feel embedded in their workflow.",
        "outcomes" => ["activation", "adoption"],
        "priority" => "low",
        "title" => "Onboarding checklist shows early drop-off after the first win",
        "type" => "issue"
      },
      %{
        "action_plan" => "The first step is to identify the moment in the user lifecycle when someone has clearly outgrown basic onboarding but has not yet been introduced to the next strategic workflow. This is often where teams assume the product will \"sell itself,\" but users still benefit from guidance. Review your existing content to see whether there is a deliberate handoff from foundational education to power-user enablement. If that handoff is missing, users may remain comfortable but under-expanded in their usage.\n\nOnce you identify that transition point, design a more intentional progression that promotes the next best action. This should not feel like repeating onboarding; it should feel like advancing the user to a more valuable stage of maturity. Consider introducing contextual prompts, milestone-based check-ins, or a short flow tied to demonstrated behavior. The recommendation should be specific, timely, and tied to a concrete gain such as saving time, improving outcomes, or unlocking a capability relevant to how the user already works.\n\nFinally, review success definitions for this stage of the journey. If your content strategy is heavily optimized for first-run activation, it may not be doing enough to support expansion and habit formation. Add goals or internal checkpoints around advanced feature exposure and progression behaviors so this stage becomes visible and manageable. By creating a clearer upgrade path inside the product experience, you can turn already-engaged users into more deeply adopted and more durable customers.",
        "actions" => [],
        "cta_text" => "Map next-step journey",
        "entity_id" => nil,
        "entity_type" => "flow",
        "expected_impact" => "Closing this progression gap could improve advanced feature adoption and strengthen retention among already-active users.",
        "finding" => "Behavior patterns suggest that users who are already **highly engaged** are not consistently being guided toward the next-value action.\n\n**Potential gap in the journey**\n1. Users complete the core onboarding path\n2. Users show repeat engagement with foundational workflows\n3. Few users appear to be pushed toward the advanced capability that would deepen adoption\n\nThis can create a plateau where users are active, but not expanding into the behaviors most associated with long-term retention and account growth.",
        "outcomes" => ["adoption", "retention", "engagement"],
        "priority" => "high",
        "title" => "Power users may be missing a key upgrade path in the product journey",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "03a77bad-1368-4b65-9431-bfaed0ee7bde",
  "workflow_key" => "insight-issue-added"
}

Meta

%{"orig_scheduled_at" => 1777573252038756, "structured" => true}

Errors

** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-issue-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Thu, 30 Apr 2026 18:22:25 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKs1ihWcZEk6zkYB1pSG"}, {"x-xss-protection", "1; mode=block"}], status: 404}}

** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-issue-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Thu, 30 Apr 2026 18:21:53 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKs1gtSWWh3XIosB9U1E"}, {"x-xss-protection", "1; mode=block"}], status: 404}}

** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-issue-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Thu, 30 Apr 2026 18:21:29 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKs1fTYSR4kz5fwAblfD"}, {"x-xss-protection", "1; mode=block"}], status: 404}}

** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-issue-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Thu, 30 Apr 2026 18:21:09 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKs1eIgu8RO0NiECNRRl"}, {"x-xss-protection", "1; mode=block"}], status: 404}}

** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-issue-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Thu, 30 Apr 2026 18:20:52 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKs1dHLTW18HaGUBSEOk"}, {"x-xss-protection", "1; mode=block"}], status: 404}}