Reviewer's Guide

Support CTA URL (link) buttons in Cloud API WhatsApp sendButtons by mapping URL buttons to WhatsApp interactive cta_url messages and preserving their display text in internal echoes, while keeping existing reply-button behavior unchanged.

Sequence diagram for WhatsApp Cloud API sendButtons CTA URL handling

sequenceDiagram
  participant Client
  participant BusinessStartupService
  participant MetaCloudAPI

  Client->>BusinessStartupService: sendMessageWithTyping(message_with_buttons)
  alt [cta_url button present]
    BusinessStartupService->>BusinessStartupService: build cta_url interactive content
    BusinessStartupService->>MetaCloudAPI: post(content, messages)
    MetaCloudAPI-->>BusinessStartupService: response with wamid
  else [no cta_url button]
    BusinessStartupService->>BusinessStartupService: build reply interactive content
    BusinessStartupService->>MetaCloudAPI: post(content, messages)
    MetaCloudAPI-->>BusinessStartupService: response with wamid
  end

Flow diagram for buttonMessage URL to cta_url mapping

flowchart TD
  A[buttonMessage receives data.buttons] --> B{button.type === url?}
  B -->|Yes| C[Create button with type cta_url]
  C --> D[Set displayText and url]
  D --> F[Return mapped buttons]
  B -->|No| E[Create button with type reply and reply.title]
  E --> F[Return mapped buttons]

File-Level Changes

Possibly linked issues

• Error sending SendButtons with a button type different from "reply" #1249: PR maps URL buttons to Cloud API cta_url, fixing the 400/TypeError when sending SendButtons with links.

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

@gomessguii @pastoriniMatheus
good improvement (needs review)

@gomessguii Ajuda a gente, cara! Isso é muito bom pra o uso da WCloud na evolution! hahaha

Some extra context for whoever picks this up, because this PR fixes a defect the tracker currently believes is already fixed.

Issue #1249 (Feb 2025) reports exactly the payload this PR handles:

{
  "number": "{{ remoteJid }}",
  "buttons": [
    { "type": "url", "displayText": "Google", "url": "https://google.com" }
  ]
}

It was closed as completed on 2025-09-09, with no closing comment and no linked fix commit. 355 issues in this repo were closed that same day, so it reads as a backlog sweep rather than a resolution.

The defect is still on develop today. In src/api/integrations/channel/meta/whatsapp.business.service.ts (L1538), every button is mapped with a hardcoded type:

buttons: data.buttons.map((button) => {
  return {
    type: 'reply',
    reply: {
      title: button.displayText,
      id: button.id,
    },
  };
}),

There is no cta_url path there. Across the whole repository cta_url appears in exactly one file — whatsapp.baileys.service.ts, the QR-code channel. So on the Cloud API channel a URL button has never been representable: it is coerced into a reply button (with id undefined for a type: "url" input) and handed to Meta in a shape it will not accept. The exact error string may have shifted since the v2.2.3 the reporter was on; the structural gap is what I verified against current develop.

That is what these 39 lines add: detect a URL button, emit the interactive / cta_url payload the Cloud API actually expects, and leave the reply-button path untouched.

CI is green and both points from the Sourcery review were addressed in dd7d91c.

cc @dpaes @agasalhem — you both asked about this one. If #1249 is worth reopening or linking, the pointer above is the evidence.