Edit Form Template Fields
Rename a form template, add fields, choose field types, require fields, and save changes.
Use the form template editor to change the reusable field structure behind a saved form template.
Edit a Template
- Open Templates > Forms.
- Select the template.
- Select Edit.
- Update the template name if needed.
- Add, remove, or update fields.
- Save the template.
After saving, Agiled returns to the template detail page.
Editing a template affects future forms created from that template. It does not automatically rebuild forms that were already created, so update live forms separately when the same change is needed there.
Field Settings
Each field row includes:
- Field label.
- Field type.
- Required toggle.
- Remove action.
Supported field types include text, email, phone, number, textarea, select, checkbox, date, and file.
Choose the field type by how the answer will be used later. Use email and phone fields for contact details, number fields for quantities or budgets, select fields for values you want to filter or report on, and textarea fields for longer context.
Add a Field
- Select Add field.
- Enter the field label.
- Choose the field type.
- Turn on Required if users must complete the field.
- Save the template.
Keep labels short and specific. A reusable template should say Project budget,
Preferred start date, or Company website instead of broad labels such as
Info or Details.
Place the most important fields near the top. Future form creators usually review the first few fields carefully and may miss optional context fields if the template is disorganized.
Remove a Field
Use the remove action on a field row. Removing a field changes future forms that start from this template. It does not automatically rewrite already-created CRM forms.
Before removing a field, check whether it is used for CRM mapping, workflow conditions, qualification, or reporting. If an old field is no longer useful, consider renaming it or making it optional before removing it from the template.
Review Before Saving
Before saving, check field order, labels, required fields, and field types. A template should be broad enough to reuse, but specific enough that future users do not need to rebuild the same structure.
Required Field Guidance
Mark a field required only when the team cannot act without it. Too many required fields reduce completion rates on public forms and slow down internal form creation.
Good required fields are usually name, email, service type, or a consent field. Optional fields are better for budget, files, notes, timelines, or details that can be collected later.
If a required field is needed only for one campaign, make it required on that specific form instead of forcing every future form created from the template to collect it.
Test The Template
After editing:
- Preview the template.
- Create a new CRM form from it.
- Confirm field order, required states, and field types.
- Submit one private test form.
- Check the created submission and mapped record.
If the form generated from the template needs many edits every time, split the template into separate use-case templates instead of keeping one generic version.
Mapping And Workflow Impact
Field labels and field types can affect CRM mapping and workflow conditions on forms created from the template. Before changing a reusable field, check whether future forms depend on that value for contact creation, deal routing, ticket creation, notifications, or automations.
When a field is used for reporting, prefer select fields over free-text fields. Select options keep values consistent so later filters and exports are easier to read.
Troubleshooting Template Edits
If a new form does not show the expected fields, confirm it was created after the template was saved. Existing forms keep their own field structure.
If submissions arrive with missing data, check whether the field was optional, whether the public form was updated, and whether the form mapping points to the right CRM or custom field.