Nifty Forms let you build clean, functional forms and collect responses without a third-party tool. Every submission can trigger a project automation, turning what someone typed into a Task, Discussion message, or Doc — already routed to the right place, with the right fields filled in.

Forms is an add-on. Workspace Owners can enable it from Workspace Settings → Workspace Add-ons.

This choice shapes the rest of the setup, so pick based on what should happen after someone hits submit. Requests that need to be worked on become Tasks; things the team should see and reply to become Discussion messages.

1. Form Name and Description Add a title and description. Both are visible to anyone filling out the form, so use them to set expectations — what this form is for, and what happens after submission.

2. Add Fields Available field types:

Use + Add Another Field to insert a field, the X to remove one, and drag-and-drop to reorder.

3. Field Descriptions Add guidance beneath any field from its options menu. This is the highest-leverage thing you can do for response quality — a bug report field that says "include the browser and what you were doing when it broke" gets you far more usable submissions than one that just says "Description."

4. Dropdown & Multi-Select Options

For fields with preset choices, use + Add Another Choice to add an option, the X to delete one, and the drag handle on the left to reorder them.

Conditional logic keeps forms short. Instead of showing everyone every possible question, you show each person only what's relevant to them. There are two types:

1. Conditional Fields Show additional fields based on earlier answers. For example, use Set Field Condition to reveal a platform selection only when someone indicates they're reporting a mobile issue.

Available conditions:

2. Conditional Placement Route the resulting Task based on how someone answered. For example, use Set List Condition to send submissions into a "Mobile Projects" list when the response indicates mobile app interest.

Placement conditions use the same operators as field conditions.

Once your fields are set, you can shape what the submitter sees after they hit submit. Choose one:

Success Message: Add a Success Title and Description. Use it to tell people what happens next and when to expect a reply — this is the last thing they see, and it's where most forms leave people guessing.

Redirect URL: Or send submitters straight to a specific URL instead.

You can also send an automatic confirmation email when a form is submitted, with content pulled from the submission itself.

Inserting Dynamic Data: Reference any form field by wrapping its name in double curly brackets. To address someone by the name they entered in your Name field, use {{Name}}.

If your form creates a Task, you can also use {{TaskID}} — a simple way to give customers a reference number for their bug report or request up front, before anyone on your team has touched it.

Note: Curly bracket codes work in the subject line as well.

Task Creation: Choose the List and Status where the Task will be created.

Sync Form and Task Fields: You can map form responses into project Custom Fields, as shown with the Email field below.

Syncing Options from Custom Fields: When you add a Dropdown field, you can pull its options from an existing project Dropdown Custom Field instead of typing them out again.

Select the Custom Field, then click Sync Options to pull its values in.

Your Dropdown responses now match the Custom Field — and stay consistent with how that data is already structured in your project.

Manage Forms: All saved Forms live in the Manage Forms tab of the Automations module.

Click into a Form to see its current status and response details. New Forms start unpublished — no one can reach them until you publish. The options menu on the right lets you Publish/Unpublish, Preview, Edit, or Delete.

Once published, you'll get a URL you can share directly or embed on your website.