Args

%{
  "account_id" => "112101",
  "data" => %{
    "account_insight_agent_id" => "4192584b-fa3c-4fed-9954-2b9db0e44e46",
    "insights" => [
      %{
        "action_plan" => "Update the published step copy so **\"V ideo\"** becomes **\"Video\"**. After updating, do a quick pass on the rest of this flow for spacing issues around punctuation, since the same flow also uses CTA text like **\"I'm Ready !\"**.",
        "actions" => [],
        "cta_text" => "Review flow copy",
        "entity_id" => "1560554a-edcf-4de0-8c3d-4f6cba5e7882",
        "entity_type" => "flow",
        "expected_impact" => "Removes an obvious copy error in a live onboarding flow and improves trust during first-use guidance.",
        "finding" => "In [Quick Capture](https://studio.appcues.com/flows/1560554a-edcf-4de0-8c3d-4f6cba5e7882/analytics), the published copy includes a clear typo:\n\n- **\"Walk Slowly - V ideo in motion requires higher bitrates.\"**\n\nThis appears to be an English formatting/spelling error rather than locale-specific copy. The likely correction is:\n\n- **\"Walk Slowly - Video in motion requires higher bitrates.\"**",
        "outcomes" => ["activation", "engagement"],
        "priority" => "high",
        "title" => "Quick Capture flow has a visible split-word typo",
        "type" => "issue"
      },
      %{
        "action_plan" => "Clean up the punctuation spacing in this tour and standardize the headline phrasing. If you want the product area named explicitly, use **\"Analytics\"** without the extra article for a more natural English reading.",
        "actions" => [],
        "cta_text" => "Review analytics tour",
        "entity_id" => "ab3d230a-f17a-44a2-8530-1de5d784fe41",
        "entity_type" => "flow",
        "expected_impact" => "Makes the analytics tour feel more polished and professional for new users.",
        "finding" => "In [Console-Analytics](https://studio.appcues.com/flows/ab3d230a-f17a-44a2-8530-1de5d784fe41/analytics), several live strings use spacing that reads as incorrect in English:\n\n- **\"Welcome to the Analytics !\"** → likely **\"Welcome to Analytics!\"**\n- **\"Would you like to take a quick tour of Analytics ?\"** → likely **\"Would you like to take a quick tour of Analytics?\"**\n- **\"You're all set !\"** → likely **\"You're all set!\"**\n\nThese look like copy issues rather than intentional locale choices.",
        "outcomes" => ["activation", "engagement"],
        "priority" => "medium",
        "title" => "Console Analytics tour has repeated English punctuation errors",
        "type" => "issue"
      },
      %{
        "action_plan" => "Fix the punctuation on the CTA, then rewrite the Present tooltip into plain English with consistent capitalization. Keep product terms like **Secondary Camera** only where they are true feature labels.",
        "actions" => [],
        "cta_text" => "Review meeting tour",
        "entity_id" => "0c9ba674-0c34-45ff-81d0-72d7b2deb1f4",
        "entity_type" => "flow",
        "expected_impact" => "Reduces friction in a live meeting walkthrough and makes instructions easier to scan in-session.",
        "finding" => "In [Meeting Tour](https://studio.appcues.com/flows/0c9ba674-0c34-45ff-81d0-72d7b2deb1f4/analytics), the live copy has at least one likely typo and one awkward phrase:\n\n- **\"I'm ready !\"** → likely **\"I'm ready!\"**\n- **\"Click on the Present to present Assets share your Desktop, or share a Secondary Camera feed.\"**\n  - likely should read something like **\"Click Present to present assets, share your desktop, or share a secondary camera feed.\"**\n\nThis appears to be English copy quality rather than a localization variant.",
        "outcomes" => ["activation", "engagement"],
        "priority" => "medium",
        "title" => "Meeting Tour includes typo-like CTA spacing and awkward copy",
        "type" => "issue"
      },
      %{
        "action_plan" => "Standardize CTA punctuation across the related camera-setup flows so exclamation marks are attached directly to the preceding word.",
        "actions" => [],
        "cta_text" => "Review related CTAs",
        "entity_id" => "a364190e-f66b-4c92-b51d-3aef6db6325c",
        "entity_type" => "flow",
        "expected_impact" => "Creates a more consistent, polished experience across linked onboarding flows.",
        "finding" => "In [Hardware Assembly](https://studio.appcues.com/flows/a364190e-f66b-4c92-b51d-3aef6db6325c/analytics), the CTA uses **\"I'm Ready !\"** with an extra space before the exclamation mark. The same pattern also appears in other live camera-setup flows, including [Quick Capture](https://studio.appcues.com/flows/1560554a-edcf-4de0-8c3d-4f6cba5e7882/analytics).\n\nFor English UI copy, the likely correction is:\n\n- **\"I'm Ready!\"**",
        "outcomes" => ["activation", "engagement"],
        "priority" => "low",
        "title" => "Hardware-related flows use inconsistent exclamation spacing",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "4bab5024-812c-4a31-8d9f-2261a80962e6",
  "workflow_key" => "insight-issue-added"
}

Meta

%{"orig_scheduled_at" => 1777558546984992, "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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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