Args

%{
  "account_id" => "34567",
  "data" => %{
    "account_insight_agent_id" => "c7566fd6-c391-46c1-b787-10c3ddb249c3",
    "insights" => [
      %{
        "action_plan" => "For **demo flow 2.0 B**, complete these items before publishing:\n\n1. **Rewrite both steps around one concrete use case**\n   - Replace the internal/demo title with a user-facing headline.\n   - Replace placeholder body text with a short explanation of the feature, workflow, or action you want the user to take.\n\n2. **Make the CTA labels outcome-based**\n   - Replace generic buttons like \"Continue\" and \"Close\" with labels tied to the next action, such as reviewing a feature, finishing setup, or going to a relevant page.\n   - Appcues examples recommend clear CTAs like \"See plans,\" \"Finish setup now,\" or other action-specific wording rather than generic progression labels  .\n\n3. **Narrow the targeting rules for demo flow 2.0 B**\n   - Replace the current any-page URL rule with the specific path(s) where this message is relevant.\n   - Add audience criteria if this is meant for a subset of users.\n   - Appcues page-targeting guidance notes that \"Any page\" will show the experience everywhere Appcues is installed unless additional rules restrict it .\n\n4. **Attach a success goal before launch**\n   - Choose the product event that represents success after seeing this flow.\n   - Set a conversion window that matches the use case so you can evaluate whether the experience influenced behavior.\n   - Appcues recommends goals for measuring conversion and comparing performance over time  .\n\n5. **Test with a small internal audience first**\n   - Keep the audience narrow for QA, validate copy and targeting, then expand only after the flow behaves as intended .",
        "actions" => [],
        "cta_text" => "Review flow draft",
        "entity_id" => "55537b52-6141-4d7c-8e84-f7d41b87d20c",
        "entity_type" => "flow",
        "expected_impact" => "Finishing these changes should turn demo flow 2.0 B from a broad draft into a measurable, relevant message that can improve activation or adoption without creating unnecessary user interruption.",
        "finding" => "I reviewed **demo flow 2.0 B** and it is not yet effective as a live user experience.\n\n- It has **2 steps**, but both steps still use placeholder body copy rather than product-specific messaging.\n- The opening headline still reads like an internal working title (**\"Demo Flow 2.0 edited in agentstudio\"**), which is not suitable for end users.\n- The CTAs are generic (**\"Continue\"**, **\"Previous\"**, **\"Close\"**) and do not tell users what value they will get next.\n- The flow is targeted to **any URL (`.*`)** with **show once** frequency, so if published in this state it could appear broadly without matching a clear use case.\n- It has **no goal attached**, which means you would only be able to track views/completions instead of whether the flow drove the intended user behavior.\n\nThat combination makes this draft hard to measure and risky to publish. Appcues guidance is to define goals for each experience and use targeting to control who sees it, where it appears, and when it triggers . The docs also explicitly recommend attaching a goal to every published experience and narrowing audience/testing before launch  .",
        "outcomes" => ["activation", "adoption", "engagement"],
        "priority" => "high",
        "title" => "Demo flow 2.0 B is still a draft template, not a launch-ready message",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "c5d18eba-39b1-4c1e-8bc2-1f6fcacb1076",
  "workflow_key" => "insight-issue-added"
}

Meta

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