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.
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.
Each source gets its own URL. Rotate it if it ever leaks.
Map paths like data.contact.email to lead and contact fields. Form-encoded bodies work too.
Update, always create, or skip, matching on email, phone, either, or lead name.
Add a signing secret and Pitch2Sale rejects anything not signed with it.
Admins can set it up.
Give it a name and, if you like, a source key so you can tell leads apart.
For each lead or contact field, enter the path in your tool's payload.
Pick On duplicate and Match on, and an optional idempotency field so repeats are ignored.
At least 8 characters. Sign each request with HMAC-SHA256.
Paste it into your form or tool as the destination.
| Direction | What | When |
|---|---|---|
| Your tool → Pitch2Sale | A lead and its primary contact, with your mapped fields and source key | Your tool posts to the URL |
| Your tool → Pitch2Sale | Updates to an existing lead, if you chose Update | The email, phone or name already exists |
| Pitch2Sale → your tool | A response saying whether the lead was created, updated or skipped | On every request |
| Not synced | Mappings are fixed after creation; make a new webhook to change them | — |
Yes. Point their webhook or HTTP step at your Receive URL. Native connectors are coming.
Up to 60 requests a minute from one address, each up to 1 MB.
Not after creation. Create a new webhook and switch your tool over.
Click Rotate URL. The old one stops working.
Create a webhook, paste the URL into your tool, and send your first lead.