FlowSync can send WordPress registrations, purchases, and form submissions into TAPNET Lead Engine using your Intake API Key.
TAPNET Lead Engine is a lead intake API rather than a list-based CRM. There are no lists or segments to pick: every lead lands in the intake source its API key belongs to, so all you configure in the builder is which WordPress fields travel with it.
Free maps the two fields TAPNET needs to create a lead. Pro opens up the rest of the intake payload, so the lead arrives already qualified and attributed instead of needing a follow-up call to find out what the person wanted.
custom_fields object.Tap any recipe to install it as a starting point — all wires connected.
WooCommerce
TAPNET Lead Engine
ProfilePress
TAPNET Lead Engine
Gravity Forms
TAPNET Lead Engine In TAPNET Lead Engine, open the intake source you want leads to land in and copy its API key. If the key is restricted to approved domains, check that your site domain or server IP is on the list, because FlowSync posts server to server with no browser origin.
Open TAPNET Lead Engine API keysGo to FlowSync → Integrations → TAPNET Lead Engine and paste the API key. Leave the intake URL blank unless TAPNET gave you a custom endpoint. You can also set a default service interest, target location, and tags that ride along with every lead.
In the workflow builder, click + Add step → TAPNET Lead Engine. TAPNET has no lists, so the destination is fixed to All leads and all you configure is the field mapping. Email is required.
Hit Run test to fire a sample payload. The run log shows the request sent to TAPNET and the response. TAPNET has no validation endpoint, so an incorrect key surfaces here as a 401 or 403 on the first lead rather than at connect time.
Install FlowSync free, paste your API key, and pick a recipe to get started.