Help

FAQ

#Which n8n versions does it support?

n8n 2.x. It was checked against the 2.47.3 node definitions and uses only built-in nodes, no community nodes.

#n8n Cloud or self-hosted?

Both. On self-hosted n8n you create a Google OAuth client once per instance (setup step 4). On Cloud, Google sign-in is one click.

#Do I need a website?

No. Publish the Demo Form workflow and share its link on a Facebook Page button, your Instagram bio, your Google Business Profile, or a QR code at the counter. Add ?utm_source=qr or similar to see which link brought each lead.

#What counts as a duplicate?

The same email (ignoring capitals), or the same phone number after cleaning, if dedupe_by_phone is on. So 0917-000-0101 and +63 917 000 0101 are the same person.

#What happens to a duplicate?

The original row is updated: submission_count goes up, last_seen_at and message are refreshed, and a note is added. If you already marked the lead contacted, qualified or won, that status stays; otherwise it becomes returning. No second thank-you email unless ack_on_duplicate is on. Your team still gets an alert, which you can turn off with alert_on_duplicate.

#Is spam stored anywhere?

No. Spam is dropped and gets a quiet 200 OK, so bots learn nothing. To review it, see Keep spam for review.

#Can I get WhatsApp, Viber or SMS alerts?

Yes. Add an output to Route Alerts and an HTTP Request or WhatsApp Business Cloud node. See Customize.

#Can I add a CRM?

Yes. Add HubSpot, Notion, Airtable or Pipedrive after Build Response & Alerts. All lead data is in $('Dedupe Check').first().json.

#Facebook Lead Ads?

Build a small parent workflow: Facebook Lead Ads Trigger → an optional Edit Fields node to rename fields → Execute Workflow calling Lead Capture → Sheet + Alerts. It arrives with trigger = subworkflow. Pass a source such as facebook-lead-ads to label it.

#Can I run several clients on one n8n?

Yes. Duplicate the workflows per client and change the webhook path, the form path and the Config values. Each client can use their own Google credential.

#How many leads a day can it handle?

Comfortably hundreds. Each run reads the whole Leads tab to find repeats, so archive old rows yearly or once the tab passes about 20,000 rows.

#Why are the credentials empty after import?

On purpose. The kit ships with no tokens or keys. You pick your own credentials on each node after importing.

#Why is the hosted form a separate workflow?

n8n 2.x won't run a Form Trigger in a workflow that also contains Respond to Webhook, and the website webhook needs Respond to Webhook to send JSON back. The Demo Form calls the main workflow, waits for it, then shows a Thank-You page, so the lead logic still lives in one place.

#Does the error handler cover form submissions?

If the main workflow fails while the Demo Form is calling it, the visitor sees the Error Page. Logging comes from the main workflow's Error Workflow setting; check the Error Log tab after your first forced test to confirm on your n8n version.

#Is the lead's data safe?

It stays in your Google account and your n8n. Credentials live in n8n's encrypted store, never in the workflow files. Mention in your privacy notice that enquiries are stored in Google Sheets and processed by n8n, as the Philippine Data Privacy Act of 2012 (and the PDPA in Singapore and Malaysia) expects.

#Does it work outside the Philippines?

Yes. Set default_country_code and timezone in Config, for example 65 and Asia/Singapore.