Home / Integrations / TAPNET Lead Engine

TAPNET Lead Engine

Send leads to your TAPNET intake source.

Integration CRM Official
Actions
1
Used on
Avg setup
3 min
Auth
Intake API key

What you can do

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.

Available actions 1 total

Leads

Send lead to TAPNET
tapnet.lead.send
Post the WordPress user to your TAPNET intake source as a lead, matched by email. TAPNET has no lists, so every lead lands in the intake source the API key belongs to.

What you can map

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.

Free
Enough to create the lead.
INCLUDED
User emailemail
Full namename
Extended field mapping
Qualification, routing, and attribution.
PRO
Phonephone
Companycompany
Service interestservice_interest
Target locationtarget_location
Callback timecallback_time
Page URLpage_url
UTM contextutm_source, utm_medium, utm_campaign, utm_term, utm_content
Plus message, preferred contact method, external ID, page title, referrer, and form ID. Anything else you map rides along in the lead's custom_fields object.

Popular workflow recipes

Tap any recipe to install it as a starting point — all wires connected.

WooCommerce TAPNET Lead Engine

Sync new WooCommerce customers to TAPNET Lead Engine, segmented by plan tier

1 action · common
ProfilePress TAPNET Lead Engine

Add new ProfilePress members to a welcome list in TAPNET Lead Engine

1 action · common
Gravity Forms TAPNET Lead Engine

Send Gravity Forms submitters to a TAPNET Lead Engine list based on form ID

1 action · common

How to set it up

1

Copy your TAPNET intake API key

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 keys
2

Connect FlowSync to TAPNET

Go 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.

3

Add the action to a workflow

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.

4

Run it, check the logs

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.

Connect TAPNET Lead Enginein minutes.

Install FlowSync free, paste your API key, and pick a recipe to get started.