Short answer: Drop the "Typeform → List Responses" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Form ID form_id | string | Required | Typeform form ID — 6-char alphanumeric. Find in the form URL: admin.typeform.com/form/<id>. |
Page Size page_size | string | Optional | Number of responses per page (max 1000) |
Since since | string | Optional | ISO 8601 date — only responses submitted after this |
Completed Only completed | options | Optional | Completed Only. Options: Yes, No (include partial) |
{"form_id": "e.g. abc123XYZ","page_size": "25","since": "e.g. 2025-01-01T00:00:00Z","completed": "{{trigger.completed}}"}
{"items": [{"answers": [{"text": "John Doe","type": "text","field": {"ref": "q1"}}],"response_id": "resp123","submitted_at": "2025-01-15T12:00:00Z"}],"page_count": 2,"total_items": 42}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.