Wishpond

Work with the Wishpond marketing automation API across leads, anonymous visitors, contact lists, and user and event tracking. Agents keep campaigns driven by real on-site behavior.

21 actions API key available

Wishpond website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

A tracked session crosses the engagement threshold the demand generation team set

List Visitor Events returns what the anonymous visitor actually did, paged at 200 events

List Leads filtered by email prefix tests whether this person already exists as a lead

The address the session offered is checked against what the capture point actually stated

The session history and the proposed identity post to the demand generation channel

A marketer confirms the promotion, and Identify User merges the anonymous history into a named lead

What This Integration Enables

Wishpond is the only platform in this group that models the person before they are a person. Leads and anonymous visitors are two parallel object types with the same shape: both can be listed, fetched, deleted, and asked for their event history and list memberships. That symmetry is the product, and it is why Wishpond leans top of funnel. The interesting behaviour is not what a known contact did after they subscribed, it is what an unknown session did on the way to becoming one.

The bridge between the two is Identify User, which attaches attributes to a client identifier and merges prior anonymous activity into the identified profile. Supplying an email attribute creates a lead if one does not already exist. Alongside it, Track Event records custom activity that can drive Wishpond workflows and appears in the lead's timeline. Both tracking operations authenticate with a separate Merchant ID and Tracking Key against Wishpond's tracking host, while leads, visitors and lists use the API token, so a workflow that only reads the funnel never needs the credentials that can write to it. Agents can do the reading, the scoring and the list maintenance at full speed. The one call that turns a pseudonymous session into a named, mailable profile is the one that stops for a person.

Without FlowRunner

Anonymous traffic is a number Pre-conversion behaviour exists only as an aggregate, so nothing can be done with it

Identity is a side effect Any workflow that touches an email quietly creates a mailable profile

List membership is guessed at An automation tries to add leads to a rule-driven list and fails without saying why

With FlowRunner

Anonymous traffic is a record Each visitor carries an event history that can be read, scored and reasoned about

Identity is a decision Promoting a visitor to a lead is a step someone approves, with the evidence attached

List membership matches the list type Static lists are written to and SmartLists are read from, because the API draws that line

Use Case Scenarios

Scoring engagement on what the lead actually did

Lead score is only useful if it reflects behaviour. The agent calls List Lead Events for each active lead, which returns page views, campaign views and custom tracked events at up to 200 per page, and builds a score from the pattern rather than from a form field. List Leads supports a date range that can be re-pointed at email open or click dates instead of creation date, so a re-engagement workflow can ask for everybody who last clicked more than sixty days ago without exporting the account. The resulting score is written back with Update Lead and pushed to the CRM in HubSpot, where sales sees the same number marketing does.

Static lists written to, SmartLists read from

Wishpond draws a hard line between the two list types, and a workflow that ignores it breaks. Static lists have manually managed membership and report a status of active; SmartLists are rule-driven, report a status of live, and leads cannot be added to or removed from them at all. So the agent calls List Lists, checks the type before it acts, and routes accordingly: Create List and Update Lead maintain the static lists a campaign targets, while List Leads In List reads a SmartList to see who the rules currently include. Delete List removes a list without deleting the leads that belonged to it, which is what makes list restructuring survivable.

Erasure requests handled across both object types

A deletion request arrives through the support desk. The agent resolves the person with List Leads by email prefix, and also checks List Visitors, because someone who browsed before converting may exist as both. Delete Lead permanently removes the lead together with every event recorded against it, and Delete Visitor does the same for the anonymous record. Both are final. The agent produces the two identifiers, the event counts attached to each, and the list memberships that will disappear, and posts them to the request ticket in Jira so the deletion is executed against a documented scope rather than a name.

Human-in-Loop Highlight

Identify User is a small call with a large consequence. It attaches attributes to a tracked client identifier, and supplying an email attribute creates a lead where none existed. What makes it different from any other create in this catalog is the merge: prior anonymous activity folds into the identified profile, so the moment the call succeeds, a browsing history that was pseudonymous five seconds ago is attached to a named person and retroactively readable. That is a real change in what the organization holds about somebody, and the agent making it usually cannot see where the address came from. An email typed into a chat widget, an address inferred from a partner cookie, and an address submitted on a form that stated what it would be used for are indistinguishable by the time they reach the workflow.

So the promotion stops and asks. The agent posts to the demand generation channel: "Visitor 8f21c has 34 tracked events across 6 sessions including 3 pricing page views. An email address surfaced from the support chat transcript, not from a capture form. Identify User would create a lead and attach all 34 events to that address permanently. Promote and attach the history, create the lead without merging prior sessions, or leave the visitor anonymous?" A marketer answers, and the human-in-the-loop step returns the choice to the flow. The agent could make this call thousands of times an hour inside Wishpond's rate limit. Whether a person consented to being known is not a throughput problem, and the platform will not answer it, so we ask someone who can.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

21 actions

Leads

List Leads Retrieves leads with paging, filtering and sorting, narrowed by status, email prefix, client identifier or a creation date range that can be re-pointed at email open or click dates instead. Returns up to 200 leads per page along with account-wide lead and visitor totals.
Get Lead Retrieves one lead by identifier with its subscription status, lead score and every custom attribute stored against it. The enrichment call before a routing or scoring decision.
Create Lead Creates a lead from an email address plus any number of custom attributes. Attribute keys should avoid spaces so they stay usable as merge tags in Wishpond emails and landing pages, which is a naming decision worth making once at the start.
Update Lead Updates a lead's attributes and optionally adds it to or removes it from a static list in the same call, changing only the attributes supplied. SmartList membership cannot be changed here, because those lists are rule-driven.
Delete Lead Permanently deletes a lead together with every event recorded against it. Final and irreversible, which is exactly what a right-to-erasure request needs and exactly why the scope belongs in front of a person first.
List Lead Events Retrieves the activity events recorded against a lead, such as page views, campaign views and custom tracked events, at up to 200 per page. The raw material behind behavioural scoring.
List Lead Lists Retrieves every list a lead currently belongs to with the list type and the date it was added. Used to audit segmentation before a campaign rather than after the send report.

Visitors

List Visitors Retrieves anonymous visitors who have not yet been converted into leads, paged at 200 per page with account-wide totals. This is the surface most marketing APIs do not expose at all.
Get Visitor Retrieves one tracked visitor by identifier, including attributes captured before any conversion. Read before deciding whether a session is worth surfacing to a person.
Delete Visitor Permanently deletes a tracked visitor and every event recorded against it. Final, and the counterpart to Delete Lead when an erasure request covers someone who never converted.
List Visitor Events Retrieves the activity events recorded against an anonymous visitor, such as visited URLs and viewed campaigns, at up to 200 per page. The evidence a promotion decision should be made on.
List Visitor Lists Retrieves every list a visitor currently belongs to with the type and join date. Confirms which campaigns are already reaching a session that has no name attached.

Lists

List Lists Retrieves the account's lists with paging and filtering. Static lists report a status of active and are manually managed; SmartLists report live and are rule-driven, and telling them apart before writing is what keeps an automation from failing silently.
Get List Retrieves one list by identifier with its type, lead count and subscription rules. The lead count is the cheapest audience size available here.
Create List Creates a static contact list. New lists start empty and are populated by adding leads through Update Lead, so list creation and list membership are two separate steps by design.
Update List Renames an existing list without affecting membership. Individual leads still move through Update Lead.
Delete List Permanently deletes a list. The leads that belonged to it survive, so only the list and its membership records are lost, which makes restructuring recoverable.
List Leads In List Retrieves the leads in a specific list with each lead's attributes and join date, paged at 200. The read path for both static lists and SmartLists.
List Visitors In List Retrieves the anonymous visitors in a specific list, paged at 200. Shows how much of a segment is still unidentified.

Tracking

Identify User Identifies a tracked user by client identifier and records attributes about them, merging prior anonymous activity into the identified profile. Supplying an email attribute creates a lead where none exists, which is why this call belongs behind a human decision. Attribute keys are limited to 64 characters and values to 256, and it requires the Merchant ID and Tracking Key rather than the API token.
Track Event Records a custom activity event against a tracked user, which can then drive Wishpond workflows and appears in the lead's event timeline. Event names are limited to 32 characters and the properties value to 256, and it uses the same tracking credentials as Identify User.

Frequently Asked Questions

What can FlowRunner do with Wishpond?

FlowRunner agents can run List Leads, Get Lead, and Create Lead in Wishpond, plus 18 more actions.

Does connecting Wishpond to FlowRunner require OAuth?

No. Wishpond connects to FlowRunner with an API key, no OAuth flow required.

Can Wishpond trigger a FlowRunner workflow automatically?

Wishpond doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Wishpond

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us