Intake that lands in the work.
Forms are intake forms tied to a project. Pick the fields, switch the form on, and each submission arrives in the project it belongs to. Add a "Form submitted" automation to send an email, create a task, or call a webhook. Automations are on paid plans.
Five things, no plumbing.
Most form tools collect data and stop. Forms collects it inside the workspace where the next step happens, so the intake queue and the work queue are the same place.
Build a form from an ordered list of fields. Give it a slug and an owner, and switch it on or off without a developer.
Each form points at a target project, so submissions arrive where the team already works instead of in a separate tool.
Start an automation on submit to create a task, update a CRM deal, send an email, or call a webhook. On paid plans.
Request an approval on a task and record the decision, so requests that need sign-off get it on the record.
Download a form's submissions as CSV at any time, or manage forms through the REST API with the same role and module permissions as the app.
Three steps, one workspace.
Forms is part of Atlas, so the form, its submissions, and the follow-up work share one workspace.
Pick the fields
Name the form, choose the target project, and add fields in order. Give it a slug and an owner, then switch it on.
Collect submissions
People fill in the form. Each submission is saved against the form and lands in the target project, ready for someone to pick up.
Act on submit
A "Form submitted" automation can create a task, update a CRM deal, send an email, or call a webhook. Automations are on paid plans.
Six features, all built in.
Each works with the rest of Atlas, with no plug-in to install.
Ordered fields
Add, reorder, and rename fields. The order holds on every submission and in the CSV export.
Target project
Every form names the project its submissions belong to, so intake never sits in a separate tool.
On or off
Switch a form off when an intake window closes and back on later. Each form has a slug and an owner.
Encrypted submissions
TLS 1.3 in transit and encryption at rest, inherited from the hosting provider, on every submission.
CSV export
Export all submissions for a form as CSV for reporting, audits, or a review in a spreadsheet.
Webhooks and API
A "Form submitted" automation can call your webhook, and the REST API lists forms and exports submissions.
Submissions route everywhere.
A form is intake. The data should not pile up in a separate database. It should arrive where the next action happens.
Five places a submission can go
A submission lands in its target project as work in Tasks. A "Form submitted" automation can update a CRM deal or call a webhook. Assignees hear about new work in Inbox. Export everything to CSV whenever you need it.
Programmatic intake.
List forms and export submissions with the REST API and a personal access token. TypeScript shown.
// List your forms, then export one form's submissions as CSV. Requires forms:read. import { writeFile } from "node:fs/promises"; const API = "https://api-atlas.wrxstack.com/v1"; const headers = { Authorization: `Bearer ${process.env.ATLAS_TOKEN}` }; // atlas_pat_... const forms = await (await fetch(`${API}/forms`, { headers })).json(); const intake = forms.find((f) => f.slug === "it-requests"); const csv = await (await fetch(`${API}/forms/${intake.id}/submissions.csv`, { headers })).text(); await writeFile("it-requests.csv", csv);
Forms vs. Typeform.
Typeform is a polished, standalone form builder. wrxstack Forms is simpler intake that puts submissions in the workspace where the work happens.
wrxstack Forms vs. Typeform
| Capability | Typeform | wrxstack Forms |
|---|---|---|
| Branching logic | Logic jumps between screens | Conditional fields: a field appears only when an earlier answer matches |
| Form design | Highly designed, one question at a time | Standard form layout |
| Where submissions go | Its own results view, plus integrations | A target project in your workspace |
| Follow-up work | Via integrations or Zapier | "Form submitted" automations, on paid plans |
| Data out | Export and integrations | CSV export and REST API |
| Tasks, CRM, and docs | Separate tools | Same workspace |
Common questions.
Six things people ask before they ship a form.
Can I import a Typeform or Google Form?
There is no documented importer for Typeform or Google Forms today. Recreate the fields in Forms and point the form at a project.
Does Forms support conditional logic or payments?
Conditional fields, yes: you can set a field to appear only when an earlier answer matches a value, for example a budget field that shows only after someone answers "Yes" to having a budget. Payments are not built in. For payment collection, use a dedicated tool and bring the results into Atlas through the REST API.
What happens after someone submits?
The submission is saved against the form and arrives in its target project. With a "Form submitted" automation, Atlas can also create a task, update a CRM deal, send an email, call a webhook, or send an SMS through the Twilio connector, which is in beta.
How are submissions protected?
Submissions travel over TLS 1.3 and are encrypted at rest, inherited from the hosting provider. Role and module permissions decide who can see them, and customer content is not used to train models.
Can I get the data out?
Yes. Export a form's submissions as CSV from Atlas or through the REST API at any time.
What about file uploads?
Forms does not host file uploads. It has a file link field, where people paste a link to a file they already store elsewhere, and the link is checked as a valid address before the form submits. If people need to complete a PDF form, PDF Studio can fill and edit it.
Pairs well with.
Forms does the most work when CRM, Tasks, and Inbox are live to pick up what comes in.
Who this is not for.
Forms turns intake into routed work. If you run large-scale market research or academic studies that need branching survey logic, response panels, quotas, and statistical export, a dedicated survey platform will fit better. If you need multi-screen logic jumps, payments, or file uploads hosted inside the form, a dedicated form builder will fit better today. Forms is built to collect intake and hand it to the team, not to run research at survey-panel scale.
Put intake where the work is.
Atlas is free to start, no credit card. Build a form, point it at a project, and switch it on.