Forms
An AI form builder for churches
Describe the sign-up you need in ordinary words and get the fields back, ready to edit. The same forms you would build by hand — just not from an empty page.
Describe the form you need in ordinary words and Psalmly generates the fields.
Edit, reorder or delete any of them before it is saved — the generated version is a starting point, never the final one. There are 9 field types, and a name, email or phone field arrives already set to fill itself in from the member’s own profile.
Forms themselves are on every plan; generating one from a description is the part a paid plan adds.
At a glance
| What it takes in | A description in words — "a camp registration with a shirt size and an emergency contact". |
|---|---|
| What it produces | Generated fields, editable before saving. 9 types: short text, long text, email, phone, number, date, single select, multi select, yes/no — with name, email and phone fields pre-filled from the member’s profile. |
| Where it runs | The admin side of Psalmly, on the web. |
| Plans | Forms are on every plan, including Free. Generating them from a description is on Community and Growth. |
How it works
Three steps, and you keep control of the last two.
Step 1
Say what the form is for
One sentence. Name the things you know you need — a shirt size, an emergency contact, a dietary note — and leave the rest to come back as a sensible default.
Step 2
Edit what comes back
Change wording, swap a field's type, reorder, delete, add. A generated form is an ordinary Psalmly form from the moment it appears — there is no separate 'AI form' to maintain.
Step 3
Attach it where it belongs
Save it to your form library, then attach it to an event — or to several. Responses collect under each attachment and export when you need them.
What you get back, and how forms fit together
The generation is the small part. The model underneath it is why one waiver can serve every trip you run.
- 9 field types
- short text, long text, email, phone, number, date, single select, multi select, yes/no. The same set you get building by hand, so nothing about a generated form is second-class.
- Fields that fill themselves in
- A person's name, an email field and a phone field arrive wired to the member's own profile, so a signed-in member starts part-answered instead of retyping what you already know.
- A form is a reusable template
- It belongs to your church, not to one event. Build a waiver once and it stays in the library, ready for the next thing that needs it.
- Attaching is a separate step
- An event can carry several forms, in order — a standing waiver plus the form for this particular trip — and the same waiver serves every event without being rebuilt.
- Responses belong to the attachment
- Never to the event. That is what lets one form be used in many places without its answers running together.
- Export when you need it
- Responses come out as a CSV, or as a PDF set in your church's own accent color rather than ours.
Where it stops
Small, deliberate limits.
It does not save anything
The generated fields sit in the builder until you save them. Nothing reaches a member before you attach it.
It builds fields, not logic
The 9 field types are what a form is made of. There is no branching, scoring or conditional page to configure.
It does not collect payment
A form gathers answers. Giving runs through your church's own Stripe account, separately and securely.
Forms are not the paid part
Building, attaching, collecting and exporting are on every plan. Only generating from a description needs Community or Growth.
Forms are on every plan, including Free.
Generating one from a description is the AI part, and that comes with Community and Growth, from $49 a month. AI is the one thing in Psalmly a paid plan buys; the rest of the app is free forever.
See what each plan includes →Questions churches ask
What do I actually type?
A sentence describing the form: "a camp registration with a shirt size and an emergency contact", or "a meal sign-up with a dish and how many people". You get fields back that match.
Can I change what it generates?
Yes, all of it. Edit the wording, change a field's type, reorder them, delete some, add your own. What comes back is a starting point, never the final form — nothing saves until you save it.
What kinds of field can it make?
9: short text, long text, email, phone, number, date, single select, multi select, yes/no. Those are the same types you get building a form by hand, so a generated form and a hand-built one are the same object afterwards.
Do members retype their details every time?
No. Name, email and phone fields come already wired to fill themselves in from the member's own profile, so a signed-in member starts most forms part-answered.
Do I need a paid plan to use forms?
No. Forms are on every plan, including Free — build them by hand, attach them to events, collect and export responses. Generating one from a description is the part that needs Community or Growth.
Can one form be used for more than one event?
Yes, and that is the point of the model. A form is a reusable template; attaching it to an event is a separate thing. One waiver can serve every trip you run, and one event can carry several forms in order.
More of Psalmly's AI
Bring your church into one home
Create your church free in an afternoon. Turn the assistant on when it would earn its keep.