Creating a Resource from a FormLister Submission

FormLister is often introduced as a form processor, but one of its more useful patterns is content creation. Instead of only sending a notification, the form can create a new resource with predefined fields, parent, and template.

Typical use cases

• reviews and feedback entries
• user-submitted listings
• support requests stored as resources
• simple front-end content workflows

What you need to define

• which parent resource will hold the new entry
• which template the created resource should use
• which submitted fields map to resource fields or TVs
• whether the new resource should be published immediately

Important editorial rule

For most public-facing forms, it is safer to create the resource unpublished and let an editor review it first. That keeps the content workflow clean and protects the site from low-quality or unwanted submissions.

Good architecture

Think of FormLister here as the input layer. Resource creation is just the output target. Once that is clear, it becomes much easier to design review queues, moderation steps, and later automation around the created content.