Args

%{
  "account_id" => "214392",
  "data" => %{
    "account_insight_agent_id" => "b23fb4f5-5da3-4151-9f1e-cf7b5957f568",
    "insights" => [
      %{
        "action_plan" => "Correct the affected sentence so the word **assinatura** renders normally, then republish if your team manages copy changes through draft review. Since this is user-facing instructional text, keeping it clean will reduce distraction and improve trust.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the web_builder update_step_content capability to update the published web flow with ID 629ccef0-a7b3-45d4-a610-bcec6bbe7919 ([Groups] Adding members manually). In step group f0c1c0d6-5681-4db7-9a4a-f764f0508b67, step 721d735a-2aef-4869-b99a-136f84fafc4f, update the RichText block currently rendering the phrase 'A a ssinatura está ativa?' so it displays 'A assinatura está ativa?' in Brazilian Portuguese. Preserve all other copy, formatting, links, buttons, and layout unchanged.",
            "title" => "Fix copy artifact in groups flow",
            "undo_prompt" => "Use the web_builder update_step_content capability to update web flow 629ccef0-a7b3-45d4-a610-bcec6bbe7919, step group f0c1c0d6-5681-4db7-9a4a-f764f0508b67, step 721d735a-2aef-4869-b99a-136f84fafc4f, and restore the affected RichText phrase from 'A assinatura está ativa?' back to the original rendered text 'A a ssinatura está ativa?'. Preserve all other copy, formatting, links, buttons, and layout unchanged."
          }
        ],
        "cta_text" => "Review typo",
        "entity_id" => "629ccef0-a7b3-45d4-a610-bcec6bbe7919",
        "entity_type" => "flow",
        "expected_impact" => "Removes a visible copy defect in a live flow, improving clarity and polish for users reading the reactivation instructions.",
        "finding" => "I reviewed the live experience **[Groups] Adding members manually** and its copy appears to be in **Brazilian Portuguese**. One phrase looks like a formatting/spelling artifact rather than a locale-specific variant.\n\nPotential typo:\n- **\"A a ssinatura está ativa?\"** → likely intended to be **\"A assinatura está ativa?\"**\n\nReview the live flow here: [Open experience](https://studio.appcues.com/flows/629ccef0-a7b3-45d4-a610-bcec6bbe7919/analytics)",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "Live onboarding flow has a visible Portuguese copy artifact",
        "type" => "issue"
      },
      %{
        "action_plan" => "Remove the extra exclamation mark so the closing sentence ends with standard punctuation. This is a quick cleanup and should also be mirrored anywhere this referral copy has been duplicated.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the web_builder update_step_content capability to update the published web flow with ID 7ef0bc3d-5a1b-471d-913e-b17b8cc06bc9 (Referral Program). In step group 9ad3deee-1726-4029-b604-931cf096fea2, step de7bf3c3-a570-4bb4-aa9c-d342e4963184, update the RichText paragraph from 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito!.' to 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito.'. Preserve all other copy, formatting, and buttons unchanged.",
            "title" => "Fix thank-you copy in referral flow",
            "undo_prompt" => "Use the web_builder update_step_content capability to update web flow 7ef0bc3d-5a1b-471d-913e-b17b8cc06bc9, step group 9ad3deee-1726-4029-b604-931cf096fea2, step de7bf3c3-a570-4bb4-aa9c-d342e4963184, and change the RichText paragraph from 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito.' back to 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito!.'. Preserve all other copy, formatting, and buttons unchanged."
          }
        ],
        "cta_text" => "Review typo",
        "entity_id" => "7ef0bc3d-5a1b-471d-913e-b17b8cc06bc9",
        "entity_type" => "flow",
        "expected_impact" => "Improves perceived quality in a live referral experience with a low-effort copy fix.",
        "finding" => "The live experience **Referral Program** is also written in **Brazilian Portuguese**, and most copy looks consistent. I found one likely typo in the thank-you step:\n\nPotential typo:\n- **\"...cartão de crédito!.\"** → likely intended to be **\"...cartão de crédito.\"**\n\nReview the live flow here: [Open experience](https://studio.appcues.com/flows/7ef0bc3d-5a1b-471d-913e-b17b8cc06bc9/analytics)",
        "outcomes" => ["engagement"],
        "priority" => "low",
        "title" => "Referral Program live flow has a punctuation typo in the thank-you step",
        "type" => "issue"
      },
      %{
        "action_plan" => "Apply the same punctuation correction here to keep both referral experiences aligned. Because this copy appears duplicated across versions, review both together whenever one is updated.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the web_builder update_step_content capability to update the published web flow with ID 4cc87832-6ba8-469a-a6c2-e5ebf1940d41 (Referral Program 2.0). In step group 55c9c276-3f03-4e4c-94b2-b1de064b87c7, step 41a863a1-8c79-45b2-ab1e-aa06a58036e2, update the RichText paragraph from 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito!.' to 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito.'. Preserve all other copy, formatting, and buttons unchanged.",
            "title" => "Fix thank-you copy in referral flow",
            "undo_prompt" => "Use the web_builder update_step_content capability to update web flow 4cc87832-6ba8-469a-a6c2-e5ebf1940d41, step group 55c9c276-3f03-4e4c-94b2-b1de064b87c7, step 41a863a1-8c79-45b2-ab1e-aa06a58036e2, and change the RichText paragraph from 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito.' back to 'Em breve, entraremos em contato caso tenha solicitado nosso benefício de recebimento em d+2 para cartão de crédito!.'. Preserve all other copy, formatting, and buttons unchanged."
          }
        ],
        "cta_text" => "Review typo",
        "entity_id" => "4cc87832-6ba8-469a-a6c2-e5ebf1940d41",
        "entity_type" => "flow",
        "expected_impact" => "Keeps duplicated referral experiences consistent and removes a small but visible polish issue.",
        "finding" => "The live experience **Referral Program 2.0** contains the same likely punctuation typo as the original referral flow:\n\nPotential typo:\n- **\"...cartão de crédito!.\"** → likely intended to be **\"...cartão de crédito.\"**\n\nReview the live flow here: [Open experience](https://studio.appcues.com/flows/4cc87832-6ba8-469a-a6c2-e5ebf1940d41/analytics)",
        "outcomes" => ["engagement"],
        "priority" => "low",
        "title" => "Referral Program 2.0 repeats the same thank-you punctuation typo",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "7f6c9555-d2c2-4e70-a854-b9d2d6ffc401",
  "workflow_key" => "insight-issue-added"
}

Meta

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