Why there is a relay
Facebook lead forms reach Zapier first. NetSuite does not accept an anonymous post, so a small Cloudflare Worker sits in between and signs each call with token based authentication. The RESTlet behind it creates the lead on the right form, with the campaign it came from and the cost of the lead.
- Facebook lead formfilled in from an ad
- Zapierthe company's own account
- Edge relaysigns the call to NetSuite
- Seen this lead?new lead in netsuite · already in not created
- Lead in NetSuitesource and lead cost attached
- Not createdlogged, nothing duplicated
- Angi leadsent to a webhook
- Field mappingaddress, service, Angi's fee
Duplicates are caught on the lead's own ID. The email only counts when that ID is missing.
The duplicate rule that was wrong
At first a lead was skipped when its email was already on file. Reading the logs I saw that this dropped returning customers with a new enquiry. Duplicates are now caught on the lead’s own ID, and the email only counts when that ID is missing. Forms for job applications are recognised and kept out of sales.
Angi
Angi has no NetSuite integration. Its leads come in through a webhook, with the name, contact details, full address, service type and Angi’s fee for the lead mapped onto the record. Angi’s own test lead came through correctly on the first run.
What it includes
- Facebook lead forms into NetSuite through a signing relay
- Angi leads into NetSuite through a webhook
- Duplicates caught on the lead’s own ID, not the email
- Job applications on the same forms kept out