Whatsable
Yes. You can see which Click-to-WhatsApp ad started a conversation, and you can put that fact to work in the tools you already run. WhatsAble passes the referral through to your custom webhook and to n8n, Make, and Zapier triggers. Persist ctwa_clid and source_id on that first inbound, then write those two values to a Sheet or a CRM.
You run the ad in Meta Ads. WhatsAble does not create it. Someone taps the creative, WhatsApp opens, and they write you. Ads Manager saw the click. WhatsApp saw the chat. The referral on that first inbound is the join. Later messages in the same chat usually drop it, so the first one is the one you keep.
What can I build with that referral?
A sales inbox that already knows the ad. The first inbound hits the webhook or the n8n, Make, or Zapier trigger. That scenario writes source_id onto the contact in your CRM. The next person who opens the chat can see which Meta ad started it, instead of guessing from the last campaign name they remember.
A weekly sheet you can actually report from. The same first inbound appends a row with ctwa_clid and source_id. You do not have to invent Sheet buttons or CRM field labels. You write the two values WhatsAble already passed, then group the week by source_id and see which creative produced chats.
A pause decision that is not a vibe. If one source_id starts plenty of chats and another starts almost none, you take that back to Meta Ads. The automation did not create the ad. It only kept the id so you could compare.
How does the automation actually run?
The path is one story. Click-to-WhatsApp ad, first inbound on WhatsAble, then the listener you already use.
In the WhatsAble dashboard, open Developer, add an endpoint URL, and enable incoming. The first Click-to-WhatsApp inbound POSTs the referral to that URL.
https://whatsable.app/integrations/webhook
n8n, Make, and Zapier triggers get the same referral. Map top-level referral on that inbound, persist ctwa_clid and source_id, and write both to a Sheet or a CRM in the same scenario.
https://whatsable.app/integrations/n8n
https://whatsable.app/integrations/make
https://whatsable.app/integrations/zapier
A WhatsAble Agent Skill is not a separate event. It sees the same Message webhooks payload, including the referral, only if that skill is on a webhook you created (create-webhook.js --type dev --url … --incoming, or --type io). Installing skills alone does not deliver the referral.
https://whatsable.app/vibe-code
Do not wait for a later reply. If you persist on message three, the referral is usually already gone.
What do I persist?
ctwa_clid is the Conversions API click id. source_id is the Meta ad or post id. Those two are enough to start tracking. This post is not a field table.
What this is not
This is not a WhatsAble ad-creation product. It is not a wa.me, QR, or website-widget path, and it is not inbox compose. It is not a claim that every later message still has the referral, and it is not a click-by-click tour of any one CRM or Sheet. It is not a claim that an Agent Skill receives the referral without a webhook you created.