Args

%{
  "account_id" => "34567",
  "data" => %{
    "account_insight_agent_id" => "45606f62-3038-420f-a3c6-f719d461c27f",
    "insights" => [
      %{
        "action_plan" => "Keep the visual/content structure, but swap the goal to a real assistant-usage event and tighten delivery to the pages and audience where assistant value is immediate. If this is meant as a feature nudge, consider simplifying it further or moving to a lighter-weight pattern for relevant post-activation users, since Appcues notes that single, contextual nudges often outperform larger announcements for adoption .",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => "d92614b4-7e51-4273-b5cf-3d3d73c74a38",
        "entity_type" => "flow",
        "expected_impact" => "Cleaner targeting and a true usage goal should make this flow easier to optimize for assistant adoption instead of test engagement.",
        "finding" => "The content is much stronger than most flows in the account: the headline is clear, the value props are concrete, and the CTA **“See what’s new”** gives users a direction. But the experience is still configured like a test: it targets **userId starts with `test`**, fires on **event1**, allows **URL regex `.*`**, and its only goal is **`event2` 3x**. That makes it hard to know whether the announcement is actually driving assistant adoption. Appcues guidance for feature announcements is to focus on **why it matters**, provide a **clear next step**, and track actual feature usage with a goal tied to that behavior  .",
        "outcomes" => ["adoption", "engagement"],
        "priority" => "medium",
        "title" => "AI Assistant announcement looks strong but measures the wrong success",
        "type" => "opportunity"
      },
      %{
        "action_plan" => "Change the CTA from a passive close to a concrete next step: launch a short tour, open the checklist, or deep-link users to the first setup task on `/home`. Then attach a goal that reflects actual activation behavior, since Appcues recommends attaching a goal to every experience you publish .",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => "e033e88e-2226-4da5-b120-914cdac5911c",
        "entity_type" => "flow",
        "expected_impact" => "Should improve activation by turning a nice first impression into measurable progress toward first value.",
        "finding" => "This draft is clean and well-scoped for **new users seen in the last 7 days** on **`/home`**, but the primary CTA **“Get started”** only closes the modal and the flow has **no goal attached**. Right now it welcomes users without moving them toward a first-value action. Appcues recommends using a welcome experience to orient users **and promote the first CTA**, then connecting that CTA to the next logical step such as a tour or activation path  .",
        "outcomes" => ["activation", "conversion"],
        "priority" => "medium",
        "title" => "Welcome to /home stops at orientation instead of activation",
        "type" => "opportunity"
      }
    ]
  },
  "notification_id" => "b294d3a5-c203-46fb-826f-60ea7f5794bc",
  "workflow_key" => "insight-opportunity-added"
}

Meta

%{"orig_scheduled_at" => 1777409213027581, "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