Hubspot->Meta webhook, correct webhook endpoint for CAPIG vs Signals

Hi,

I’m trying to send Qualified Lead events from HubSpot to Meta using Stape, and I’m stuck on identifying the correct webhook ingestion endpoint .

Context:

  • Source: HubSpot workflow (server-side)
  • Trigger: Contact property Inbound lead qualified = Yes
  • Goal: Send a QualifiedLead event to Meta Conversions API
  • Payload (simplified):

What I’ve tried:

  • Created a Signals Gateway sgw.stape.ltd, gateway ID + API key available)

  • Also have a Meta CAPIG gateway set up in Stape

  • In HubSpot, I’ve tested POST requests to:

  • All attempts return 404. (backend NotFound), service rules for the path non-existent

My confusion:

  • Signals Gateway UI shows a URL + API key, but seems to be meant for browser/pixel ingestion, not raw webhooks
  • CAPIG appears to be the correct product for server-to-server (HubSpot → Meta) events
  • However, I cannot find a clear, explicit webhook/ingestion URL for CAPIG in the UI, and generic endpoints (e.g. /v1/event) don’t work

My questions:

  1. Can Signals Gateway accept raw server-side webhooks from HubSpot at all, or is it pixel-only?
  2. For Meta CAPIG, what is the correct ingestion endpoint for sending server-side events from a CRM like HubSpot?
  3. Is the CAPIG endpoint gateway-specific / region-specific, and where exactly in the UI can I find it?
  4. Is there an official example (curl / Postman) for HubSpot → CAPIG → Meta?

I want to avoid guessing URLs and make sure I’m using the product as intended.

Thanks in advance — any clarification from the Stape team or experienced users would be hugely appreciated.

Hello there,

  1. Neither Meta CAPIG not Signals will accept raw webhooks, they will accept non-pixel signal, but it needs to be formatted as a CAPI request:
  • note: in case of Signals you need the Signals Pixel ID, not Meta Dataset ID
  1. We have long since abstracted all of this and offer a free HubSpot application that fits your scenario:

Thank you so much for this Dan, very helpful!

I’m not quite there yet though.

Here’s what I’ve done so far:

  • I’ve installed the Stape hubspot app and added the required input for CAPI gateway. (This was done last week, so it’s been running a few days now).
  • I’ve selected a specific Hubspot Lead status that should fire an event.
  • I’ve left the Meta Lead ID input field blank as it’s not mandatory
  • I’ve triple checked that I’m referencing the right Meta Dataset ID and Stape API key.

Even so, I can’t detect any matching new events in Meta. Can you provide any more guidance here?

@elin how exactly are you checking and what are the event names you’re sending? Have you confirmed said events ( I assume custom ones) in your dataset (pixel) interface?

Hi Dan! Thanks for bearing with me here.

I’m checking in my meta dataset interface yes, the event is called QualifiedLead. I know that the lead status change has happened in dozens of cases automatically and I’ve also changed it manually to try and trigger an event. But nothing shows in meta.

I know that the lead status change has happened in dozens of cases automatically and I’ve also changed it manually to try and trigger an even

Just to make sure, app reacts to Lead Status, not Lifecycle Stage:

can you please re-confirm that it’s the status that changed over the course of you having the app active? If that is the case, I would ask you to please DM me the API key you’re using so that we may investigate further.

Hi again Dan,
I’ve noted it’s lead status, not lifecycle stage. And yes, definitely seen cases during the course the app was installed. I’ve also tried re-installing the app but doesn’t seem to make a difference.

Happy to DM, can’t find where to do that though.

when you click on my avatar there’s a blue Message button in the pop-up

I have tried all parts of the community, when I click your avatar it looks like this

Just email me at dan@stape.io then :slight_smile: thx