Connect Halo AI to Konektor

A webhook is a private URL that Halo AI uses to send message and ad referral data to Konektor. Konektor uses that data to record new contacts as leads. To send Click-to-WhatsApp (CTWA) conversions to Meta, complete the separate Meta setup after the webhook is working.

Before you begin

Prepare the following:

  • owner or admin access to your Konektor workspace;
  • access to the webhook settings in Halo AI;
  • one WhatsApp number that you can use to send a test message.

For CTWA conversion tracking, you also need:

  • a Konektor WhatsApp Session with the same business number;
  • a Meta account with access to the WhatsApp Business Account (WABA);
  • the WABA ID for that business number.

A WABA is the Meta business account that contains your WhatsApp number. When you connect Meta, Konektor asks Meta to select the CTWA dataset already associated with the WABA or create one if needed. You do not need to find or enter a Dataset ID.

If a partner is your only connection

Do not create an unofficial WhatsApp Session just to enable CTWA. If the business number does not have a matching Session in Konektor, contact Support before you continue.

Connect the Halo AI webhook

1. Create the Halo AI integration

  1. Sign in to Konektor and open Integrations.
  2. Open the partner integrations page.
  3. Select Add Integration.
  4. Select Halo AI.
  5. Enter an Integration Name, such as Halo AI - Demo Store.
  6. Select Connect.

Konektor does not ask for a Halo AI API key at this stage.

2. Copy the webhook URL

  1. Find the Halo AI integration card that you just created.
  2. Select View Webhook URL.
  3. Copy the displayed URL.

This URL is unique to your workspace and must remain private. Do not include it in documentation, public support tickets, or messages that other people can read.

3. Add the webhook in Halo AI

  1. Open the webhook settings in your Halo AI account. The menu name may differ between Halo AI interfaces.
  2. Add a webhook for incoming WhatsApp messages.
  3. Paste the URL from Konektor.
  4. Save the changes.

Check that leads arrive

  1. Send a new message from your test number to the business WhatsApp number.
  2. Open Leads in Konektor.
  3. Confirm that the contact from the test message appears as a lead.
  4. Return to the Halo AI integration card and check Last sync.

The webhook is working when the new lead appears and Last sync changes. The Connected status on the card only confirms that the integration configuration exists; it does not prove that Halo AI has delivered a message.

Enable CTWA conversion tracking

Skip this section if you do not run Click-to-WhatsApp ads. The Halo AI webhook can include the ad click ID, but it does not give Konektor permission to send events to Meta. Konektor receives that permission when you connect the WABA.

  1. Confirm that your business-owned Meta App and token owner can access the WABA that contains the Halo AI number.
  2. Open WhatsApp > Sessions, then create or complete the Session with the same number.
  3. Select Save Changes.
  4. Select Set up CTWA on the saved Session row. Select Manage CTWA if the Session was previously connected.
  5. Enter the WhatsApp Business Account ID in the CTWA modal.
  6. Select Meta App token, paste the token into the secure modal, then select Verify and connect.

Use a System User token for continued production use. Use a Graph API Explorer token only for a limited test. Never send the token through chat, email, support tickets, documentation, or screenshots.

Follow the Meta CTWA connection guide for App requirements, both required permissions, rotation, disconnection, and migration to Meta login.

Test one CTWA conversion

  1. Open the CTWA ad as a prospective customer, then send a new message.
  2. Confirm that the message creates a new lead in Konektor.
  3. Record one conversion for that lead.
  4. Open Conversion > Sync Logs and check the delivery channel and status.

The Meta CTWA badge identifies the dedicated CTWA channel. The badge is not acceptance proof. An accepted status on a Meta CTWA row proves that Meta accepted the dedicated event. CTWA fallback identifies the regular Meta CAPI fallback. These results do not prove that Ads Manager reported or attributed the conversion.

Troubleshooting

Leads do not arrive

  1. Make sure the webhook URL in Halo AI matches the URL shown under View Webhook URL.
  2. Make sure the Halo AI webhook is active for incoming messages.
  3. Send a new message; an older message will not start a new test.
  4. Check whether Last sync changes and whether a lead appears.

If neither changes, contact Support with the test time and integration name. Do not send the complete webhook URL.

The conversion shows CTWA fallback or skipped

Konektor uses the Meta CAPI fallback when the dedicated CTWA connection is not ready. An older entry can remain skipped if Konektor processed it before the fallback became available.

Confirm that the lead came from a new message sent through a CTWA ad. Open WhatsApp > Sessions > Manage CTWA, then select Check connection.

After you correct the setup, create one new conversion. Resend uses these rules:

  • A CTWA fallback row with accepted or failed status can be eligible.
  • A Meta CTWA row with terminal failed status can be eligible.
  • A row with queued, sending, or retry status is not eligible.
  • An accepted Meta CTWA row blocks a duplicate dedicated resend for the same event and dataset.
  • A regular Meta CAPI row does not offer CTWA resend.

The WABA cannot connect to the dataset

If Konektor reports that the WABA or dataset is unavailable, do not keep selecting the button. Check that:

  • your Meta account can access the WABA;
  • the WABA ID belongs to the correct business account;
  • the token has both CTWA permissions listed in the Meta CTWA guide.

If all three are correct, contact Support. Include the Session name, attempt time, and safe message shown. Do not send a token, password, complete WABA ID, Dataset ID, or webhook URL.

There is no Session with the same number

You cannot currently connect CTWA directly from the Halo AI integration page. Contact Support so the number and WABA ownership can be checked. Do not create an unofficial Session just to bypass this step.

Halo AI or another partner manages the WABA

Using a partner does not replace Meta authorization. Ask the partner or Business Portfolio administrator to grant the required access to your Meta account and confirm the WABA ID. Meta selects or creates the CTWA dataset when you connect the account. If they cannot grant access, ask the partner to coordinate with Konektor Support before you try to connect the WABA.

Need More Help?

Our team is ready to help you maximize ad tracking and business attribution.

© 2026 Konektor. All rights reserved.