Args

%{
  "account_id" => "34567",
  "data" => %{
    "account_insight_agent_id" => "45606f62-3038-420f-a3c6-f719d461c27f",
    "insights" => [
      %{
        "action_plan" => "Unpublish or fully rewrite this experience before it reaches any broader audience. If you keep it, replace every sample reference with product-specific copy, remove broken/test redirects, and turn the final CTA into one clear next step tied to real product value. For feature discovery, Appcues recommends short, value-led guidance rather than broad multi-step interruption .",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => "-LAPrimGxetg3yyKPsWN",
        "entity_type" => "flow",
        "expected_impact" => "Reduces credibility risk immediately and prevents users from seeing irrelevant or broken guidance.",
        "finding" => "This published flow still contains obvious sample/test content across multiple steps: **Slack emoji** announcement copy, **“Hi Austin… I’m Luis… at GreatCo”**, a tooltip about **favorite dog pictures**, a **google.com** button, and a flow-level redirect to **yahoo.com**. It also includes visible copy issues like **“OK, Got ijt!”** and **“Whatkeverr.”** That kind of stale live content erodes trust, and Appcues explicitly recommends regularly reviewing published content and unpublishing stale experiences so outdated targeting or copy doesn’t interfere with better content .",
        "outcomes" => ["engagement", "adoption"],
        "priority" => "high",
        "title" => "Outdated sample content is still live in Search CTA",
        "type" => "issue"
      },
      %{
        "action_plan" => "Fix the segment before publishing this flow. Rebuild **Beginners** using explicit signals like signup recency, plan, role, setup progress, or completion/non-completion of key onboarding events. Once that’s stable, keep the flow but make the CTA route into a beginner-specific path so the message and audience stay aligned.",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => "cc0fa7c1-8547-480c-873e-959637f539cf",
        "entity_type" => "flow",
        "expected_impact" => "Better audience quality should increase relevance and reduce the chance of showing beginner messaging to the wrong users.",
        "finding" => "The content itself is polished, but its audience logic is not trustworthy. The attached **Beginners** segment resolves to an empty wildcard property condition (`property: \"\"`, operator `*`), so the persona definition is effectively meaningless. That makes it impossible to know whether the message is reaching true beginners or just an accidental catch-all. Appcues playbooks recommend defining onboarding audiences with real properties/events that indicate stage and recency, not vague labels unsupported by real criteria .",
        "outcomes" => ["activation", "engagement"],
        "priority" => "medium",
        "title" => "Beginner Welcome Flow targets a broken persona segment",
        "type" => "issue"
      },
      %{
        "action_plan" => "Either archive this draft or convert it into a real use case with a narrow audience, concrete copy, and a matching goal. If you keep it as a reusable template, rename it clearly as a template/test item so it isn’t confused with production-ready content.",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => "6591176d-0cce-41d2-9ed2-338d14235275",
        "entity_type" => "flow",
        "expected_impact" => "Reduces accidental-publish risk and keeps your experience library cleaner and easier to manage.",
        "finding" => "Both steps still use explicit placeholder text such as **“Replace this copy with your intro message or announcement”** and **“Use this space for a follow-up explanation or call to action.”** The rule also targets **URL regex `.*`** with **no goals**, which means it is not safe for live use and not measurable if it ever is published. Appcues recommends starting each experience with one specific use case and outcome, then attaching a matching goal before publishing  .",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "demo flow 2.0 A is still placeholder content with broad targeting",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "8cb51bbb-81e0-4629-b7e7-7b9ecb0b3446",
  "workflow_key" => "insight-issue-added"
}

Meta

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

Errors

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4