KoBoToolbox n8n integrationAutomate KoBoToolbox with n8n.

Uploads a file to a form, either from binary data the workflow already carries or from a public link.

• Form Name or ID: the form that receives the file, chosen from the dropdown or passed as an ID through an expression.
• File Upload Mode: two choices, Binary File when the file travels inside the item, URL when KoBoToolbox should fetch it itself.
• Property Name: the binary property holding the file. Supported types are image, audio, video, csv, xml and zip.
• File URL: the HTTP(s) link to the file, used in URL mode.

Removes one file from a form, by its identifier.

• File ID: the uid of the file, which starts with af, for example afQoJxA4kmKEXVpkH6SYbhb. It is the identifier, not the file name.
• Form Name or ID: the form the file belongs to, since the same workflow may juggle several.

Reads a file already attached to a form and can bring its content into the workflow as binary data.

• File ID: the uid starting with af, often taken from a previous node with {{ $json.field }}.
• Download File Content: whether the content is downloaded into a binary property, or not.
• Property Name: the name of the binary property the file is written into.

Lists the files attached to a form, with a single parameter to fill.

• Form Name or ID: the only required field here. Pick the form from the list, and the node returns its files.

Returns a single form from the account.

• Form Name or ID: the form to read. The dropdown is the fast path; the expression syntax is the one to use when the ID comes from an earlier node.

Walks through the forms of the account and returns them as items.

• Return All: on, the node chains the API pages until every form is back; off, it stops at Limit.
• Limit: the maximum number of forms returned when Return All stays off.
• Filter: in Options, a text search on form data, for example owner__username:meg AND name__icontains:quixotic.
• Sort: in Options, the ordering criteria applied to the result.

Redeploys the current version of a form from the workflow.

• Form Name or ID: the form to redeploy, named once in the node and reused on every run.

Returns a single hook definition declared on a form.

• Hook ID: the identifier of the hook, which starts with h, for example hVehywQ2oXPYGHJHKtqth4.
• Form Name or ID: the form carrying that hook.

Lists the hooks declared on one form, so you can see what that form is wired to.

• Return All: on, every hook of the form comes back; off, the node stops at Limit.
• Limit: the ceiling applied when Return All is left off.

Fetches the logs of a hook, with filters to narrow down what came back.

• Hook ID: the hook whose logs you want, identifier starting with h.
• Log Status: All, Failed, Pending or Success.
• Start Date and End Date: the minimum and the maximum date of the logs retrieved, which is how you keep a check focused on one window instead of replaying the whole history.

Relaunches every failed attempt of a given hook in a single call, so a backlog of errors clears without the workflow walking through the logs one by one.

• Hook ID: the hook whose failed attempts are replayed.
• Form Name or ID: the form the hook is attached to.

Replays one precise attempt instead of the whole batch.

• Hook Log ID: the log to replay, identifier starting with hl, for example hlSbGKaUKzTVNoWEVMYbLHe.
• Hook ID: the hook that log belongs to.

Erases a single submission from a form.

• Submission ID: a number, for example 245128, not the respondent's name.
• Form Name or ID: the form holding that submission.

Retrieves one submission and its data, with a set of options to shape the response.

• Submission ID: the numeric identifier of the submission, often passed as {{ $json.field }} from an earlier node.
• Fields to Retrieve: a comma-separated list such as _submission_time,_submitted_by. Left blank, all fields come back.
• Reformat: applies the reformatting logic, including parsing GeoJSON coordinates.

Collects the submissions of a form in bulk, which is the operation most exports are built on.

• Return All: on, the node pages through every submission; off, it stops at Limit.
• Filter: None or JSON, and with JSON selected, Filters (JSON) carries the query.
• Sort: in Options, sort predicates in MongoDB JSON format, for example {"_submission_time":1}.

Tells you where one submission stands in the review process, without touching it.

• Submission ID: the numeric identifier of the submission being checked.
• Form Name or ID: the form it was submitted to.

Writes the review decision back onto the submission, so the status lives in the data rather than in a conversation.

• Validation Status: Approved, Not Approved or On Hold, the three values the node accepts.
• Submission ID: the numeric identifier of the submission being updated.