Magic links are URLs that trigger Tallyfy actions automatically when a logged-in user clicks them. You can create links to:
Required kick-off fields
Magic links can’t bypass required kick-off form fields. If your template has required fields, the magic link will fail because it tries to start the process without showing the form. Workarounds:
| Action | What it does |
|---|---|
| Create one-off task | Creates a standalone task |
| Launch a process | Starts a new process from a template |
| Complete a task | Completes a specific task |
| Reopen a task | Re-opens a completed task |
| Write comment to a task | Adds a comment to a specific task |
| Edit task deadline | Updates the due date of a task |
| Update form field value | Changes a form field value on a task |
A link to launch a process and pre-fill data follows this pattern:
https://go.tallyfy.com/[YourOrgID]/process/[TemplateID]/create?default_run_name=Your+Process+Name&ko_fields=[{"fieldName1":"Value1"},{"fieldName2":"Value2"}]&launchprocess=true[YourOrgID] and [TemplateID] with your actual IDs.default_run_name sets the process name (max 550 characters).ko_fields contains kick-off field names and values to pre-fill as JSON.+ or %20).ko_fields JSON - [{"field-name":"field-value"}] - must also be URL-encoded.Use this format for ko_fields values (before URL-encoding):
| Field type | Example JSON value |
|---|---|
| Short/Long text | "Your Text Value" |
| Dropdown | {"id":ID,"text":"Selected Label","value":null,"required":true} (get ID from template editor) |
| Checkbox | [{"id":ID,"text":"Checked Label","value":null,"required":false,"selected":true}] |
| Radio button | "Selected Radio Value" |
| Date/Time | "YYYY-MM-DDTHH:mm:ss.SSSZ" (UTC format) |
Replace [YourOrgID] and [TaskID] with your actual values. All task-based actions use the /:org_id/magic URL path.
...?action=createOotTask&default_task_name=Review+Doc...?action=completeTask&task_id=[TaskID]...?action=reOpenTask&task_id=[TaskID]...?action=writeAComment&task_id=[TaskID]&comment=Please+review...?action=editDeadline&task_id=[TaskID]&deadline=YYYY-MM-DDTHH:mm:ss.SSSZ...?action=updateFormFieldValue&task_id=[TaskID]&form_fields={"fieldId123":"New+Value"}You can pre-fill fields on public kick-off forms using the same ko_fields and default_run_name parameters. The public form URL follows this pattern:
https://go.tallyfy.com/[YourOrgID]/public/kickoff/[TemplateAlias]?ko_fields=[JSON]&default_run_name=[Name]This is useful when you want to embed application links on your website with specific values pre-selected - for example, pre-filling a property name based on which listing page the visitor clicked from.
Field value format reference (before URL-encoding):
| Field type | JSON format in ko_fields | Example |
|---|---|---|
| Short text | "fieldAlias": "value" | "first-name": "John" |
| Long text / Textarea | "fieldAlias": "value" | "notes": "Line 1" |
| Dropdown | "fieldAlias": {"id": N, "text": "Label"} | "property-name": {"id": 4, "text": "16 Laurel"} |
| Radio button | "fieldAlias": "Selected Label" | "housing-type": "BPDA" |
| Checkbox / Multiselect | "fieldAlias": [{"id": N, "text": "Label", "selected": true}] | "unit-sizes": [{"id": 1, "text": "Studio", "selected": true}] |
| Date | "fieldAlias": "YYYY-MM-DDTHH:mm:ss.SSSZ" | "app-date": "2026-03-05T00:00:00.000Z" |
"fieldAlias": "email@example.com" | "contact": "john@example.com" |
Practical example - embedding on a property listing website:
<a href="https://go.tallyfy.com/ORG_ID/public/kickoff/waitlist-app?ko_fields=%7B%22property-name%22%3A%7B%22id%22%3A4%2C%22text%22%3A%2216%20Laurel%22%7D%7D&default_run_name=Application%20-%2016%20Laurel"> Request Application</a>When a visitor clicks this link, they enter their email for verification, then see the kick-off form with the property name already selected. The same ko_fields JSON format works for both logged-in and public kick-off forms.
Launching > Launch from a form
Triggers > Launch via a kick-off form