Can Zapier, Make or n8n trigger on Typeform partial responses?

What this check means

The canonical job is a trigger: start a workflow when Typeform sends a partial response to an integration. A platform is native for it only if its own Typeform integration does that exact job. API requests, generic webhooks, community nodes and custom code are recorded separately and never count as native.

Triggering on regular responses is a different canonical operation, New Response. It is native on all three platforms (Zapier: New Entry, A_DIRECT; Make: Watch Responses / Watch Responses (Instant), A_DIRECT; n8n: Typeform Trigger, A_DIRECT), but that record is not evidence for partial responses.

Why Zapier is YES

The record does not point to a trigger labelled for partial responses. It maps the job to an option on Zapier's general Typeform trigger: New Entry — Partial Responses option. The evidence note says so directly: “Canonical job is supported by an official native capability, but mapping relies on a filter/parameter/generic native module rather than a one-to-one label.” This is why the evidence is B_STRONG (clear but indirect), while Zapier's plain New Entry trigger is A_DIRECT for regular responses.

The record also ties the YES to two conditions on the Typeform side:

Typeform plan

Typeform Basic plan or higher required to send partial responses to integrations.

Recorded configuration

Enable 'Send partial responses to integrations' and use New Entry with Partial Responses.

Native class

Verified native: present in the platform's official directory or docs; who maintains the integration is not established

Delivery

Instant undisclosed: instant (labelled instant by the platform; mechanism not disclosed)

Support status

Active

Evidence

B_STRONG, checked 2026-10-07: zapier.com/apps/typeform/integrations

If the Typeform account is below that plan or the setting is off, this record does not support a YES.

Supporting help-center sources

The plan, the setting and when the trigger fires are stated in 3 help articles, recorded as supporting evidence next to the Zapier directory. Help-center evidence is itself classed B_STRONG, so it confirms the YES without making it A_DIRECT. Per Typeform's Zapier article, the trigger fires each time a respondent passes a Partial Submit Point.

• New Entry (Instant) — trigger from partial responses (help.zapier.com/hc/en-us/articles/8495992982029-How-to-get-s… · B_STRONG · checked 2026-10-07)Zapier help, updated 01 Oct 2026: 'If you want to trigger from partial responses, you must be on a Basic Typeform plan or higher and enable 'Send partial responses to integrations' in your Typeform account settings.'
• Activate your trigger with a partial response (help.typeform.com/hc/en-us/articles/360029258552-Connect-Typef… · B_STRONG · checked 2026-10-07)Typeform help: a full or partial response can trigger Zapier; 'The partial response activates the trigger each time a respondent passes a Partial Submit Point.' Requires 'Send partial responses to integrations' in the form's settings.
• Collect partial responses — integrations (help.typeform.com/hc/en-us/articles/21102221958676-Collect-par… · B_STRONG · checked 2026-10-07)Typeform help: 'To collect partial responses, you'll need a Basic plan or higher' (Partial Submit Points; 'Capture partial responses after every question' is a separate Growth/Enterprise setting). Zapier is listed among the integrations that can receive partial response data.

Why Make is UNKNOWN

Make has a native Typeform response trigger. It is recorded as native for New Response (Watch Responses / Watch Responses (Instant), A_DIRECT, delivery webhook). For partial responses the reviewed source is recorded as Watch Responses (partial semantics undocumented): Current official Make module list documents Watch Responses but does not state whether partial responses are emitted with the same semantics.

The record's condition rules out the shortcut: “Do not infer support from the existence of a generic response trigger.” Nor does the evidence show that the trigger excludes them. So the record is held open: “Official evidence is relevant but insufficient to prove or disprove exact canonical semantics; frozen as UNKNOWN.”

This is not a finding that Make cannot handle partial responses. Native class, delivery mode and support status are all UNKNOWN for the same reason. Evidence C_PARTIAL, checked 2026-10-07: apps.make.com/typeform.

Why n8n is UNKNOWN

n8n has a native Typeform response trigger. It is recorded as native for New Response (Typeform Trigger, A_DIRECT, delivery webhook). For partial responses the reviewed source is recorded as Typeform Trigger (partial semantics undocumented): Current Typeform Trigger documentation reviewed does not establish partial-response semantics.

The record's condition rules out the shortcut: “Do not infer partial events from normal response webhook support.” Nor does the evidence show that the trigger excludes them. So the record is held open: “Official evidence is relevant but insufficient to prove or disprove exact canonical semantics; frozen as UNKNOWN.”

This is not a finding that n8n cannot handle partial responses. Native class, delivery mode and support status are all UNKNOWN for the same reason. Evidence C_PARTIAL, checked 2026-10-07: docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes….

What is known, and what is not inferred