WebsitePublisher Trigger icon

WebsitePublisher Trigger

Triggers when new leads are captured on your WebsitePublisher.ai website. Polls the leads API at the configured interval.

WebsitePublisher Trigger

AI-generated

Summary

Polls WebsitePublisher for newly captured leads and emits each unseen lead as an n8n item. Configure the polling schedule and required WebsitePublisher API credentials; optionally filter results to a form name.

Inputs

  • Poll Times (required) — Choose one or more polling schedules, such as every minute, on a specific day or weekday, or with a custom cron expression.
  • Trigger Event (required) — Select the event to watch. The only available event is New Lead.
  • Form Name Filter — Optionally limit leads to a specific form name; leave empty to include all forms.
  • WebsitePublisher API credentials (required) — Credentials provide the project ID and API token used to request leads.

Output shape

A list of n8n items, one per newly detected lead, with each lead in the item's json field; returns no items when no new leads are found.

Each poll requests up to 100 leads with status new, using the last poll date when available. It filters results to IDs above the highest previously seen ID and stores that ID and the current date for later polls. The configured form name is sent as a filter when non-empty.

Examples

Example 1: Exact-key matching

Use a specific Poll Times schedule and optionally set Form Name Filter to the exact form name whose leads you want to process. Trigger Event is New Lead, the only available event. Connect WebsitePublisher API credentials containing the project ID and API token. The node requests up to 100 leads with status new, adds the prior poll date as a lower date bound when available, and sends the form name when configured. It emits one item per returned lead whose ID is greater than the highest ID previously seen, then stores the current date and highest emitted ID for later polls. This is only a partial-newness detector, not a guaranteed exact-once trigger: it does not read triggerEvent in poll(), does not paginate, and its API request uses date-only date_from values, so leads sharing an ID range, falling outside the first page, or arriving on the stored date may be skipped or repeated depending on API ordering and filtering.

Links

Discussion