Inbound webhooks

Give any form, landing page or no-code tool a private URL to post leads to. Map its fields to yours, pick how duplicates are handled, and sign the requests if you want proof they came from you.

CategoryLead capture
Data flowYour tool → Pitch2Sale
SetupBuilt in
PlansEssentials, Growth and Scale
How a lead arrives

Any tool that can POST, one lead record

Your tool posts JSON or form data to your private URL. Pitch2Sale checks the signature if you set one, maps the fields and files the lead.

Your landing page

POST /ingest/webhook/…

data.contact.emaildana@aperturelabs.io
data.companyAperture Labs
Sent
Pitch2Sale · Lead NewCreated

Aperture Labs

Sourcewebhook
Contactdana@aperturelabs.io
DuplicateNo
  1. 01Your tool posts a lead to the private URL you created.
  2. 02If you set a signing secret, the signature is checked first.
  3. 03Your field mapping turns the payload into a lead and its contact.
  4. 04Repeats with the same ID are ignored, and duplicates follow your rule.
  5. 05The lead is created or updated and scored, and the response says which.

What it does in Pitch2Sale

01 · One URL per source

Private and rotatable

Each source gets its own URL. Rotate it if it ever leaks.

02 · Field mapping

Nested JSON is fine

Map paths like data.contact.email to lead and contact fields. Form-encoded bodies work too.

03 · Duplicates

Your rule

Update, always create, or skip, matching on email, phone, either, or lead name.

04 · Signed

Optional HMAC

Add a signing secret and Pitch2Sale rejects anything not signed with it.

Set it up

  1. Open Settings → Developer → Inbound Webhooks.

    Admins can set it up.

  2. Click New webhook.

    Give it a name and, if you like, a source key so you can tell leads apart.

  3. Map the fields.

    For each lead or contact field, enter the path in your tool's payload.

  4. Choose duplicate handling.

    Pick On duplicate and Match on, and an optional idempotency field so repeats are ignored.

  5. Add a signing secret (optional).

    At least 8 characters. Sign each request with HMAC-SHA256.

  6. Click Create and copy the Receive URL.

    Paste it into your form or tool as the destination.

What syncs, and what does not

DirectionWhatWhen
Your tool → Pitch2SaleA lead and its primary contact, with your mapped fields and source keyYour tool posts to the URL
Your tool → Pitch2SaleUpdates to an existing lead, if you chose UpdateThe email, phone or name already exists
Pitch2Sale → your toolA response saying whether the lead was created, updated or skippedOn every request
Not syncedMappings are fixed after creation; make a new webhook to change them—

Common questions

Can I use this with Zapier, Make or n8n?

Yes. Point their webhook or HTTP step at your Receive URL. Native connectors are coming.

How fast can I send?

Up to 60 requests a minute from one address, each up to 1 MB.

Can I change the mapping?

Not after creation. Create a new webhook and switch your tool over.

What if my URL leaks?

Click Rotate URL. The old one stops working.

If it can POST, it can make a lead.

Create a webhook, paste the URL into your tool, and send your first lead.